Triple
T37704914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azes II |
E939173
|
entity |
| Predicate | ruledAround |
P31299
|
FINISHED |
| Object | turn of the 1st century BCE/CE |
—
|
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: turn of the 1st century BCE/CE | Statement: [Azes II, ruledAround, turn of the 1st century BCE/CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledAround Context triple: [Azes II, ruledAround, turn of the 1st century BCE/CE]
-
A.
ruledInAge
Indicates that a person held ruling power or authority during a specified historical age or period.
-
B.
ruledFromCentury
chosen
Indicates that a ruling or governance relationship is associated with a specific century during which it took place.
-
C.
ruledOnBy
Indicates that a decision, case, or matter has been formally decided or adjudicated by a specific authority or decision-maker.
-
D.
ruledDuringReignOf
Indicates that one entity exercised ruling authority or governance during the time period in which another entity’s reign took place.
-
E.
ruledUntilCentury
Indicates that a ruling relationship held by an entity continued in effect up to (but not necessarily including) 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.