Triple
T9463035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zenobia |
E228197
|
entity |
| Predicate | reignedInCentury |
P31299
|
FINISHED |
| Object | 3rd century |
—
|
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: 3rd century | Statement: [Zenobia, reignedInCentury, 3rd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignedInCentury Context triple: [Zenobia, reignedInCentury, 3rd century]
-
A.
ruledUntilCentury
Indicates that a ruling relationship held by an entity continued in effect up to (but not necessarily including) a specified century.
-
B.
cameToPowerInCentury
Indicates that an entity assumed ruling authority or control during a specified century.
-
C.
ruledFromCentury
chosen
Indicates that a ruling or governance relationship is associated with a specific century during which it took place.
-
D.
flourishedInCentury
Indicates that an entity experienced its peak activity, influence, or development during a specified century.
-
E.
existedInCentury
Indicates that an entity existed or was present during a specified century.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcd9794819093c392489d4efbe9 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.