Triple
T8270644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ladies' singles figure skating |
E193418
|
entity |
| Predicate | includesElementType |
P63681
|
FINISHED |
| Object | jumps |
—
|
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: jumps | Statement: [ladies' singles figure skating, includesElementType, jumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesElementType Context triple: [ladies' singles figure skating, includesElementType, jumps]
-
A.
hasElementType
chosen
Indicates that something is composed of or contains elements that are of a specified type.
-
B.
includesElement
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
C.
followsElementType
Indicates that one element type comes directly after another element type in a defined order or sequence.
-
D.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from another entity.
-
E.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb795243fc8190a66afef7476e1147 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:50 p.m.