Triple
T6850840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formula 2 Championship |
E158009
|
entity |
| Predicate | runsOnCircuits |
P42379
|
FINISHED |
| Object | permanent road courses |
—
|
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: permanent road courses | Statement: [Formula 2 Championship, runsOnCircuits, permanent road courses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsOnCircuits Context triple: [Formula 2 Championship, runsOnCircuits, permanent road courses]
-
A.
numberOfCircuits
Indicates the total count of circuits associated with or contained in a given entity or system.
-
B.
performingCircuit
Indicates that an entity is carrying out or executing a specific circuit, such as a sequence of connected paths, routes, or tasks.
-
C.
servesCircuit
Indicates that an entity provides legal representation or service in a specified judicial circuit.
-
D.
circuitUsed
chosen
Indicates that a particular circuit is utilized or employed in performing an action, process, or function.
-
E.
usesCircuitsAlsoUsedBy
Indicates that one entity makes use of electrical circuits that are also utilized by another entity.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84c45708190918adfc028252400 |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.