Triple
T12769294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yas Marina Circuit |
E305202
|
entity |
| Predicate | hasLongStraight |
P30563
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Yas Marina Circuit, hasLongStraight, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongStraight Context triple: [Yas Marina Circuit, hasLongStraight, yes]
-
A.
hasStartFinishStraight
Indicates that something includes a straight segment that serves as both the starting and finishing section of a course or track.
-
B.
circuitHasLongStraight
chosen
Indicates that a circuit includes at least one long, uninterrupted straight section.
-
C.
hasStraightLines
Indicates that the related entity possesses or is characterized by straight, non-curved lines.
-
D.
isMostlyStraight
Indicates that an entity is predominantly but not entirely straight in orientation, alignment, or form.
-
E.
hasLongStretchIn
Indicates that something extends for a considerable or continuous distance within a specified area, medium, or context.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df3b2f88190b37b696400178795 |
completed | April 10, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.