Triple
T7280678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippodrome of Constantinople |
E163136
|
entity |
| Predicate | factionSystem |
P75375
|
FINISHED |
| Object | chariot racing factions |
—
|
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: chariot racing factions | Statement: [Hippodrome of Constantinople, factionSystem, chariot racing factions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionSystem Context triple: [Hippodrome of Constantinople, factionSystem, chariot racing factions]
-
A.
faction
Indicates that an entity is formally affiliated with, or belongs to, a particular faction or organized group within a broader context.
-
B.
factionSymbol
Indicates the specific faction with which an entity is associated or aligned.
-
C.
fleetStrategy
Indicates the overarching plan or approach governing how a group of vehicles or vessels is organized, deployed, and operated to achieve specific objectives.
-
D.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
E.
starSystem
Indicates a relationship where an astronomical object or location belongs to, is part of, or is located within a particular star system.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb34fe0c8190a642fd3339f0cacd |
completed | March 27, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e82b0f9881909d29c99af1ea0dbf |
completed | March 27, 2026, 8:27 p.m. |
Created at: March 27, 2026, 2:59 p.m.