Triple
T805737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vine |
E17427
|
entity |
| Predicate | reasonForShutdown |
P11350
|
FINISHED |
| Object | business decision by Twitter |
—
|
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: business decision by Twitter | Statement: [Vine, reasonForShutdown, business decision by Twitter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForShutdown Context triple: [Vine, reasonForShutdown, business decision by Twitter]
-
A.
reasonForDiscontinuation
chosen
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
B.
permanentShutdown
Indicates that an entity has been irreversibly taken out of operation and will not be restarted or resumed in the future.
-
C.
reasonForDisbandment
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
-
D.
reasonForElimination
Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
-
E.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.