Triple
T18156637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Crown of Motorsport |
E434647
|
entity |
| Predicate | involvesDifferentContinents |
P121330
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Triple Crown of Motorsport, involvesDifferentContinents, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesDifferentContinents Context triple: [Triple Crown of Motorsport, involvesDifferentContinents, true]
-
A.
crossesContinent
Indicates that one entity traverses from one side of a continent to the other, passing across its landmass.
-
B.
continentCrossed
Indicates that an entity has traversed from one side of a continent to the other, crossing the continent’s landmass.
-
C.
otherContinent
chosen
Indicates that two entities are located on different continents from one another.
-
D.
locatedInTranscontinentalCountry
Indicates that an entity is situated within a country whose territory spans more than one continent.
-
E.
geographicallySeparatedFrom
Indicates that two places or regions are distinct and apart from each other in physical location or geographic space.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4debe27a88190bd76c6f78fcf1bd1 |
completed | April 19, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.