Triple
T37384915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panther Racing |
E928539
|
entity |
| Predicate | operatedFromState |
P6602
|
FINISHED |
| Object | Indiana |
E32567
|
NE 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: Indiana | Statement: [Panther Racing, operatedFromState, Indiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedFromState Context triple: [Panther Racing, operatedFromState, Indiana]
-
A.
operatedFrom
chosen
Indicates that an entity conducted its activities or operations starting from or based at a particular location or source.
-
B.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
C.
operatedBefore
Indicates that one entity performed an operation or action at an earlier time than another entity.
-
D.
isOperatedIn
Indicates that an entity carries out its operations or activities within a specified location, region, or jurisdiction.
-
E.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
- F. None of above.
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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02fb5ca96081908ff618f560011940 |
completed | May 12, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4076ed34148190a2cd8c01987ee867 |
completed | June 28, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_6a02f9602b308190a97f81821e12b13f |
completed | May 12, 2026, 9:56 a.m. |
Created at: May 3, 2026, 4:16 p.m.