Triple
T14651634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | centre (ice hockey) |
E343999
|
entity |
| Predicate | requiresAttribute |
P42360
|
FINISHED |
| Object | stamina |
—
|
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: stamina | Statement: [centre (ice hockey), requiresAttribute, stamina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresAttribute Context triple: [centre (ice hockey), requiresAttribute, stamina]
-
A.
requiresProperty
chosen
Indicates that one entity depends on another entity possessing a specific property or attribute in order for a condition, action, or relationship to hold.
-
B.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
C.
requiresPresence
Indicates that one entity’s existence, operation, or validity depends on another entity being present or available.
-
D.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
E.
requiredOn
Indicates that one entity must exist, be present, or be fulfilled on a specific other entity, date, or condition as a mandatory requirement.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb517e7648190b9fc73d6cdbb68de |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.