Triple
T23013291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firestone Grand Prix of St. Petersburg |
E572962
|
entity |
| Predicate | circuitLayoutIncludes |
P56265
|
FINISHED |
| Object | city streets |
—
|
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: city streets | Statement: [Firestone Grand Prix of St. Petersburg, circuitLayoutIncludes, city streets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circuitLayoutIncludes Context triple: [Firestone Grand Prix of St. Petersburg, circuitLayoutIncludes, city streets]
-
A.
hasCircuitLayout
chosen
Indicates that one entity possesses, includes, or is associated with a specific circuit layout design of another entity.
-
B.
includesCircuitType
Indicates that one entity contains or makes use of a specified type or category of circuit.
-
C.
circuitDesigner
Indicates that an entity is responsible for designing or creating electronic circuits for another entity or 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e300008190bb12c6388a8b3280 |
completed | April 29, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.