Triple
T5112640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old French sire |
E115252
|
entity |
| Predicate | descendantInEnglish |
P3437
|
FINISHED |
| Object | sir |
—
|
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: sir | Statement: [Old French sire, descendantInEnglish, sir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descendantInEnglish Context triple: [Old French sire, descendantInEnglish, sir]
-
A.
modernLanguageDescendant
Indicates that one language is a direct or indirect descendant of another language in the modern era.
-
B.
hasEnglishName
chosen
Indicates that an entity is associated with a name expressed in the English language.
-
C.
descentFrom
Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
-
D.
hasDescendantPeople
Indicates that one entity has other people as its descendants in a genealogical or lineage-based relationship.
-
E.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75cba1e88190af076657f846b975 |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.