Triple
T7515797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MilleMiglia |
E177639
|
entity |
| Predicate | statusCriterion |
P12363
|
FINISHED |
| Object | miles flown |
—
|
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: miles flown | Statement: [MilleMiglia, statusCriterion, miles flown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusCriterion Context triple: [MilleMiglia, statusCriterion, miles flown]
-
A.
statusQualificationMetric
chosen
Indicates a metric that qualifies, evaluates, or characterizes the status or condition of something in a measurable way.
-
B.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5f595148190b36649b0095bb898 |
completed | March 27, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:45 p.m.