Triple
T15384289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koopa Troopa Beach |
E367878
|
entity |
| Predicate | hasLapCount |
P42384
|
FINISHED |
| Object | 3 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: 3 laps | Statement: [Koopa Troopa Beach, hasLapCount, 3 laps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLapCount Context triple: [Koopa Troopa Beach, hasLapCount, 3 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.
typicalRaceDistanceLaps
chosen
Indicates the usual number of laps that constitute the standard race distance for a given racing event or category.
-
C.
hasDialCount
Indicates that an entity possesses or is associated with a specific number of dials.
-
D.
hasNumberOfTrails
Indicates the specific count of trails associated with or available in a given entity.
-
E.
hasCountingPeriod
Indicates that there is a defined time span or interval over which occurrences, quantities, or measurements related to an entity are counted or aggregated.
- 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.