Triple
T15384524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wario Stadium |
E367883
|
entity |
| Predicate | hasStartFinishLine |
P78948
|
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: [Wario Stadium, hasStartFinishLine, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartFinishLine Context triple: [Wario Stadium, hasStartFinishLine, yes]
-
A.
hasStartFinishStraight
chosen
Indicates that something includes a straight segment that serves as both the starting and finishing section of a course or track.
-
B.
isFinishLineOf
Indicates that something serves as the finish line or endpoint for a particular event, race, or process.
-
C.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
D.
hasLandmarkAtEnd
Indicates that a landmark is located at the terminal point or end of a specified path, route, or boundary.
-
E.
hasStraightLines
Indicates that the related entity possesses or is characterized by straight, non-curved lines.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7397188190bde42b897ab4b5b4 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.