Triple
T29038987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | women's 100 metres |
E737941
|
entity |
| Predicate | finishCriterion |
P29156
|
FINISHED |
| Object | torso crossing finish line |
—
|
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: torso crossing finish line | Statement: [women's 100 metres, finishCriterion, torso crossing finish line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishCriterion Context triple: [women's 100 metres, finishCriterion, torso crossing finish line]
-
A.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
B.
finishOption
Indicates that one entity represents a way, method, or configuration by which another entity is completed, finalized, or brought to its end state.
-
C.
finish
Indicates that an entity brings an action, process, or state to an end or completion.
-
D.
finishSetting
Indicates that an entity completes configuring or establishing a particular setting or set of settings for another entity or context.
-
E.
terminationCondition
chosen
Indicates the condition or set of conditions under which an ongoing process, activity, or relationship is brought to an end.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603f2f88819080e922efd5f23f04 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 10 a.m.