Triple
T3571088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyrus of Alexandria |
E75571
|
entity |
| Predicate | officeStartAsPatriarchOfAlexandria |
P50629
|
FINISHED |
| Object | c. 630 |
—
|
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: c. 630 | Statement: [Cyrus of Alexandria, officeStartAsPatriarchOfAlexandria, c. 630]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeStartAsPatriarchOfAlexandria Context triple: [Cyrus of Alexandria, officeStartAsPatriarchOfAlexandria, c. 630]
-
A.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
-
B.
ancientPolisCenter
Indicates that a location functioned as the central urban, political, or social hub of an ancient polis (city-state).
-
C.
majorPharaoh
Indicates that the subject is recognized as a principal or highly significant pharaoh in relation to the object (such as a period, dynasty, or context).
-
D.
urbanPrefectOfRomeStart
Indicates the time at which a person begins serving as the Urban Prefect of Rome.
-
E.
startEmperor
Indicates that an entity begins its role, reign, or status as an emperor.
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0c32624819097a96b3d62e3d8f0 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb8364d848190a96a9bc7a6126af2 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adba25c66c81909a05a97327828c41 |
completed | March 8, 2026, 6:04 p.m. |
Created at: March 8, 2026, 3:21 p.m.