Triple
T3046525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MON |
E83462
|
entity |
| Predicate | usedForTeamSport |
P17094
|
FINISHED |
| Object | ice hockey |
—
|
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: ice hockey | Statement: [MON, usedForTeamSport, ice hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForTeamSport Context triple: [MON, usedForTeamSport, ice hockey]
-
A.
usedInSport
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
-
B.
associatedWithTeamSport
chosen
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
-
C.
usedByTeam
Indicates that something (such as a resource, tool, or method) is utilized or employed by a particular team.
-
D.
usedInTeamStatisticsFor
Indicates that something (such as a metric, value, or record) is utilized in compiling or calculating statistical information for a specific team.
-
E.
usedForTeamInState
Indicates that something serves as a team or is utilized by a team within a specified state or jurisdiction.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bab541c8190a17aca26b3dcfae7 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.