Triple
T4125303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antioch on the Orontes |
E92709
|
entity |
| Predicate | rankInRomanEast |
P54428
|
FINISHED |
| Object | second only to Alexandria |
—
|
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: second only to Alexandria | Statement: [Antioch on the Orontes, rankInRomanEast, second only to Alexandria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInRomanEast Context triple: [Antioch on the Orontes, rankInRomanEast, second only to Alexandria]
-
A.
rankIn1962RomanCalendar
Indicates the position or ordering of something within the 1962 Roman Calendar.
-
B.
positionInTetrarchy
Indicates the specific role or rank an individual holds within a four-part governing or leadership structure (a tetrarchy).
-
C.
ordinalNumberAsEmperor
Indicates the numerical order in which a person held the title or role of emperor.
-
D.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
E.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af0245adbc81908b89a40850047975 |
completed | March 9, 2026, 5:24 p.m. |
Created at: March 9, 2026, 3:41 p.m.