Triple
T15535337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushroom City |
E370324
|
entity |
| Predicate | hasLapStructure |
P119069
|
FINISHED |
| Object | three laps |
—
|
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: three laps | Statement: [Mushroom City, hasLapStructure, three laps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLapStructure Context triple: [Mushroom City, hasLapStructure, three laps]
-
A.
hasLapRecordCategory
Indicates that an entity holds or is associated with a specific category or type of lap record (e.g., fastest lap under certain conditions or classifications).
-
B.
hasPitLane
Indicates that a racing circuit, track, or similar facility includes a designated pit lane area for vehicle servicing and related activities.
-
C.
hasLateralStructure
Indicates that one entity possesses or exhibits a structural feature oriented to or located on its side(s).
-
D.
hasLacing
Indicates a relationship where one entity is fastened, joined, or secured to another using laces or a lacing mechanism.
-
E.
typicalRaceDistanceLaps
Indicates the usual number of laps that constitute the standard race distance for a given racing event or category.
- F. None of above. chosen
Provenance (4 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:06 a.m.