Triple
T5272814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | go! (Hawaii) |
E119300
|
entity |
| Predicate | operationsCeased |
P17360
|
FINISHED |
| Object | April 1, 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: April 1, 2014 | Statement: [go! (Hawaii), operationsCeased, April 1, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationsCeased Context triple: [go! (Hawaii), operationsCeased, April 1, 2014]
-
A.
ceasedOperation
chosen
Indicates that an entity has stopped functioning, operating, or carrying out its activities, typically in a permanent or indefinite manner.
-
B.
ceasedOperationsAs
Indicates that an entity stopped functioning or operating in a particular role, capacity, or status.
-
C.
officeSuspendedUnder
Indicates that an individual’s official position or duties are temporarily halted under the authority or jurisdiction of a specified entity or rule.
-
D.
maintenance
Indicates that an entity performs, requires, or is involved in upkeep, repair, or preservation activities for another entity or system.
-
E.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.