Triple
T33320087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United BusinessFirst |
E853112
|
entity |
| Predicate | approximatePhaseOutEndYear |
P61876
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [United BusinessFirst, approximatePhaseOutEndYear, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePhaseOutEndYear Context triple: [United BusinessFirst, approximatePhaseOutEndYear, 2019]
-
A.
finalPhaseOutBeganYear
Indicates the calendar year in which the process of completely discontinuing or eliminating something officially began.
-
B.
plannedShutdownYear
Indicates the year in which an entity is scheduled or planned to be shut down or taken out of operation.
-
C.
hasDiscontinuationApproxYear
chosen
Indicates that an entity ceased to exist, operate, or be available around a specified (approximate) calendar year.
-
D.
plannedEndYear
Indicates the calendar year in which an activity, project, or plan is intended or scheduled to be completed.
-
E.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
Created at: May 1, 2026, 1:33 a.m.