Triple
T7170093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAR |
E167171
|
entity |
| Predicate | abbreviationUsedIn |
P62615
|
FINISHED |
| Object | NHL standings |
—
|
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: NHL standings | Statement: [CAR, abbreviationUsedIn, NHL standings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbreviationUsedIn Context triple: [CAR, abbreviationUsedIn, NHL standings]
-
A.
abbreviationUsedFor
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
-
B.
abbreviation
Indicates that one term is a shortened or contracted form that stands for another, longer expression.
-
C.
abbreviationContext
chosen
Indicates that one term is used as an abbreviation specifically within the contextual scope defined by another term or resource.
-
D.
usesAbbreviationIn
Indicates that an entity is referred to by an abbreviated form within a specified context, source, or representation.
-
E.
usedInAbbreviationMeaning
Indicates that something (typically a word, term, or symbol) is employed as part of the meaning or expansion of an abbreviation.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85d8f208190915f6f4c05988b63 |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1ce5f048190808c378a980f7bb6 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:48 p.m.