Triple
T5671126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greens |
E124978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman chariot racing faction |
C18564
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ancient Roman chariot racing faction Context triple: [Greens, instanceOf, ancient Roman chariot racing faction]
-
A.
event in ancient Rome
An event in ancient Rome is a specific occurrence or happening—such as a political assembly, religious festival, public spectacle, or military action—situated in Roman society and time that holds social, cultural, or historical significance.
-
B.
ancient Roman
An ancient Roman is a person from the civilization of Rome between roughly the 8th century BCE and the 5th century CE, characterized by its distinctive language, culture, politics, and engineering achievements.
-
C.
charioteer
A charioteer is a person who drives and controls a chariot, often in contexts such as ancient warfare, ceremonial processions, or competitive racing.
-
D.
client state of the Roman Empire
A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
-
E.
member of the Roman equestrian order
A member of the Roman equestrian order was a wealthy, property-owning citizen of the second-highest social class in ancient Rome, ranking below senators and often serving in administrative, financial, and military roles.
- F. None of above. chosen
Provenance (1 batch)
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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:43 p.m.