Triple
T5331434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chagossians |
E123317
|
entity |
| Predicate | forcedDisplacement |
P707
|
FINISHED |
| Object | late 1960s |
—
|
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: late 1960s | Statement: [Chagossians, forcedDisplacement, late 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedDisplacement Context triple: [Chagossians, forcedDisplacement, late 1960s]
-
A.
civilianDisplacement
chosen
Indicates the forced or compelled movement of civilian populations from their homes or usual places of residence, typically due to conflict, violence, or persecution.
-
B.
displacedPeopleEstimate
Indicates an estimated number of people who have been forced to leave their homes or usual places of residence due to a particular event or situation.
-
C.
displacedBy
Indicates that one entity has been moved, replaced, or forced out of its original position, role, or state by another entity.
-
D.
plannedDisplacement
Indicates a deliberate, pre-arranged movement or relocation of an entity from one place or state to another.
-
E.
majorResettlementArea
Indicates that a location serves as a primary or significant destination area where people are being resettled.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85aab0308190990626cbc9da3e21 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.