Triple
T34803839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yas Marina 12 Hours |
E1003293
|
entity |
| Predicate | usesCircuitLayout |
P42379
|
FINISHED |
| Object | Yas Marina Grand Prix layout |
—
|
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: Yas Marina Grand Prix layout | Statement: [Yas Marina 12 Hours, usesCircuitLayout, Yas Marina Grand Prix layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCircuitLayout Context triple: [Yas Marina 12 Hours, usesCircuitLayout, Yas Marina Grand Prix layout]
-
A.
hasCircuitLayout
Indicates that one entity possesses, includes, or is associated with a specific circuit layout design of another entity.
-
B.
hasCircuitLayoutType
Indicates that an entity is associated with or characterized by a specific type or category of circuit layout.
-
C.
usesCircuitType
Indicates that one entity employs or is implemented using a specific type of 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 3, 2026, 3:59 p.m.