Triple
T26362973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Prix de Trois-Rivières |
E660256
|
entity |
| Predicate | hasCircuitName |
P128403
|
FINISHED |
| Object | Circuit Trois-Rivières |
—
|
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: Circuit Trois-Rivières | Statement: [Grand Prix de Trois-Rivières, hasCircuitName, Circuit Trois-Rivières]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCircuitName Context triple: [Grand Prix de Trois-Rivières, hasCircuitName, Circuit Trois-Rivières]
-
A.
circuitName
chosen
Indicates that a specific name or label is assigned to a given circuit.
-
B.
hasCircuit
Indicates that an entity is equipped with, contains, or is associated with an electrical or logical circuit.
-
C.
isCircuitFor
Indicates that one entity functions as a circuit designed, used, or intended for another entity.
-
D.
isCircuit
Indicates that an entity functions as or constitutes an electrical or logical circuit within a system.
-
E.
hasCircuitRole
Indicates that an entity participates in a circuit with a specific functional role or responsibility within that circuit.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 10:53 p.m.