Triple

T28700507
Position Surface form Disambiguated ID Type / Status
Subject NHL forwards E729537 entity
Predicate typicalLineComposition P196216 FINISHED
Object center and two wingers 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: center and two wingers | Statement: [NHL forwards, typicalLineComposition, center and two wingers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalLineComposition
Context triple: [NHL forwards, typicalLineComposition, center and two wingers]
  • A. formedLine
    Indicates that an entity has arranged itself or others into a line or linear formation.
  • B. traditionalComposition chosen
    Indicates that something is created or arranged according to established, customary, or historically rooted methods or styles.
  • C. lineStandard
    Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
  • D. definedLine
    Indicates that a specific line (such as a boundary, path, or reference line) has been formally established or specified within a given context.
  • E. builtLine
    Indicates that an entity constructed or established a particular line, such as a route, boundary, or infrastructure segment.
  • 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_69f043e6e9688190b6bdd6e5665498ff completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_6a0115fb84448190b8b67a5ace7b289a completed May 10, 2026, 11:34 p.m.
PD Predicate disambiguation batch_6a0114ef60a081908f8db7868cf29b2f completed May 10, 2026, 11:29 p.m.
Created at: April 28, 2026, 5:42 a.m.