Triple
T18513327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemieux |
E452396
|
entity |
| Predicate | hasAbandonmentType |
P53614
|
FINISHED |
| Object | government-organized relocation |
—
|
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: government-organized relocation | Statement: [Lemieux, hasAbandonmentType, government-organized relocation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbandonmentType Context triple: [Lemieux, hasAbandonmentType, government-organized relocation]
-
A.
abandonmentType
chosen
Indicates the specific manner or category of how something or someone was abandoned in the described situation.
-
B.
abandonedBefore
Indicates that one entity ceased or gave up on something prior in time to another entity doing so.
-
C.
abandonedReason
Indicates the reason or cause for which something was abandoned, discontinued, or given up.
-
D.
abandonedDuring
Indicates that one entity ceased support for or deserted another entity in the midst of an ongoing process, event, or period.
-
E.
periodOfAbandonment
Indicates a time span during which something is left unused, unattended, or not maintained.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53348274c8190a82861b0104538e3 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.