Triple
T11099921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriarch of Antioch |
E262475
|
entity |
| Predicate | hasMultipleSuccessions |
P97277
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Patriarch of Antioch, hasMultipleSuccessions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleSuccessions Context triple: [Patriarch of Antioch, hasMultipleSuccessions, yes]
-
A.
hasSuccession
Indicates that one entity follows or replaces another in a sequence, order, or position, forming a succession relationship between them.
-
B.
hasLineOfSuccession
Indicates that one entity is designated to follow or replace another in a defined order of succession.
-
C.
hasBusinessSuccession
Indicates that one business entity continues, replaces, or inherits the operations, rights, or obligations of another business over time.
-
D.
supportedSuccessionOf
Indicates that one entity actively endorsed or helped bring about the transfer of power, position, or role from a predecessor to a successor.
-
E.
hasGenerations
Indicates a relationship where an entity is associated with one or more successive generational levels or cohorts derived from it.
- F. None of above. chosen
Provenance (4 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a29ee6c819092bc0da3f9255389 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.