Triple
T13797965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lillehammer Olympic Bobsleigh and Luge Track |
E331563
|
entity |
| Predicate | hasStartHouse |
P111502
|
FINISHED |
| Object | bobsleigh start |
—
|
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: bobsleigh start | Statement: [Lillehammer Olympic Bobsleigh and Luge Track, hasStartHouse, bobsleigh start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartHouse Context triple: [Lillehammer Olympic Bobsleigh and Luge Track, hasStartHouse, bobsleigh start]
-
A.
hasHouses
Indicates that one entity possesses, controls, or contains one or more houses in relation to another entity or context.
-
B.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
-
C.
hasStageHouse
Indicates that a performance venue or theater includes or is equipped with a stage house as part of its structure.
-
D.
hasNumberOfHouses
Indicates the quantity of houses associated with a given entity.
-
E.
hasPublicHouse
Indicates that one entity possesses, operates, or is associated with a public house (such as a bar or pub) as part of its facilities or holdings.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025be1f08190aac525d72d7dc0c3 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:11 p.m.