Triple
T467984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabriel |
E8490
|
entity |
| Predicate | isBiblicalName |
P7172
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Gabriel, isBiblicalName, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBiblicalName Context triple: [Gabriel, isBiblicalName, true]
-
A.
biblicalName
chosen
Indicates that one entity is the name of a person, place, or concept as it appears in the Bible.
-
B.
hasLiturgicalName
Indicates that an entity is associated with a specific name used in liturgical or religious worship contexts.
-
C.
hasNameInHebrew
Indicates that an entity is associated with a specific name expressed in the Hebrew language.
-
D.
hasBiblicalConnection
Indicates a relationship in which one entity is connected to another through references, themes, origins, or influences derived from the Bible.
-
E.
isTheophoric
Indicates that something (typically a name or term) incorporates the name of a deity or refers explicitly to a god.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd9bea081909ee782840f3da12b |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edebb3988190907992a584b4e260 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.