Triple
T24692042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luge World Cup events |
E611466
|
entity |
| Predicate | determineBy |
P7593
|
FINISHED |
| Object | combined run times |
—
|
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: combined run times | Statement: [Luge World Cup events, determineBy, combined run times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: determineBy Context triple: [Luge World Cup events, determineBy, combined run times]
-
A.
determinedBy
chosen
Indicates that one entity’s state, value, or outcome is decided, controlled, or fully specified by another entity.
-
B.
determinativeFor
Indicates that one entity serves to uniquely identify, specify, or determine the status, interpretation, or outcome of another entity.
-
C.
canDetermine
Indicates that one entity has the ability or authority to find out, establish, or decide the state, value, or outcome of another entity or situation.
-
D.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
-
E.
determinesRepresentativeFor
Indicates that one entity selects or designates another entity to act as its representative in a given context.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:20 a.m.