Triple
T20157124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humber—St. Barbe—Baie Verte |
E491599
|
entity |
| Predicate | abolishedInDecade |
P30300
|
FINISHED |
| Object | 2010s |
—
|
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: 2010s | Statement: [Humber—St. Barbe—Baie Verte, abolishedInDecade, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishedInDecade Context triple: [Humber—St. Barbe—Baie Verte, abolishedInDecade, 2010s]
-
A.
abolishedDuring
chosen
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
-
B.
demolishedInDecade
Indicates that something was demolished during a specified decade.
-
C.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
D.
dateAbolished
Indicates the date on which something (such as an institution, law, practice, or position) was officially ended or abolished.
-
E.
wasAbolishedInContextOf
Indicates that something (such as a law, practice, institution, or position) was formally ended or eliminated specifically within, or as part of, a particular event, process, or broader situational context.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e18a0c8190a2cc2b305da28047 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:34 p.m.