Triple
T30485963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild |
E775720
|
entity |
| Predicate | hasAbbreviationInContext |
P127294
|
FINISHED |
| Object | MIN (for Minnesota Wild in NHL standings) |
—
|
NE NERFINISHED |
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: MIN (for Minnesota Wild in NHL standings) | Statement: [Wild, hasAbbreviationInContext, MIN (for Minnesota Wild in NHL standings)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbbreviationInContext Context triple: [Wild, hasAbbreviationInContext, MIN (for Minnesota Wild in NHL standings)]
-
A.
isAbbreviation
Indicates that one term is a shortened or abbreviated form of another term.
-
B.
hasAbbreviationStatus
Indicates that an entity has a particular status or condition regarding its abbreviation (e.g., whether it is abbreviated, how, or to what extent).
-
C.
mayBeAbbreviatedIn
Indicates that one expression can be represented as an abbreviation within another expression or context.
-
D.
hasAbbreviationOrForm
chosen
Indicates that one entity serves as an abbreviation, shortened form, or alternative written form of another entity.
-
E.
isUsedInAbbreviation
Indicates that one entity functions as a shortened or abbreviated form of another entity.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687456090819099bbbb33f6c2c048 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:13 p.m.