Triple
T22584213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Las Vegas Wranglers |
E564741
|
entity |
| Predicate | announcedOperationsSuspension |
P128529
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Las Vegas Wranglers, announcedOperationsSuspension, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedOperationsSuspension Context triple: [Las Vegas Wranglers, announcedOperationsSuspension, 2014]
-
A.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
-
B.
suspendedFrom
Indicates that one entity is hanging or held up in the air by being attached to another supporting entity.
-
C.
shutdownAnnouncedOn
chosen
Indicates that an official announcement was made on a specific date or platform that a system, service, or operation will be shut down.
-
D.
announcedPermanentClosure
Indicates that an entity has formally stated that it will cease operations or availability indefinitely and not reopen.
-
E.
ceasedOperation
Indicates that an entity has stopped functioning, operating, or carrying out its activities, typically in a permanent or indefinite manner.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1615b4fa08190a8d2d66e01db429f |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:44 p.m.