Triple
T26505968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCR International Series |
E669543
|
entity |
| Predicate | notableCircuitPresence |
P51142
|
FINISHED |
| Object | Sepang International Circuit |
—
|
NE NERFINISHED |
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: Sepang International Circuit | Statement: [TCR International Series, notableCircuitPresence, Sepang International Circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCircuitPresence Context triple: [TCR International Series, notableCircuitPresence, Sepang International Circuit]
-
A.
notableCircuit
chosen
Indicates that an entity is recognized as a significant or noteworthy circuit, such as an important electrical, racing, or logical circuit.
-
B.
hasCircuit
Indicates that an entity is equipped with, contains, or is associated with an electrical or logical circuit.
-
C.
isCircuit
Indicates that an entity functions as or constitutes an electrical or logical circuit within a system.
-
D.
circuitUsed
Indicates that a particular circuit is utilized or employed in performing an action, process, or function.
-
E.
belongsToCircuit
Indicates that something is a component or member of a specific circuit or circuit grouping.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: April 27, 2026, 1:16 a.m.