Triple
T4664849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dugong Creek settlement |
E102819
|
entity |
| Predicate | hasRelocationType |
P42185
|
FINISHED |
| Object | government-planned resettlement |
—
|
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-planned resettlement | Statement: [Dugong Creek settlement, hasRelocationType, government-planned resettlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelocationType Context triple: [Dugong Creek settlement, hasRelocationType, government-planned resettlement]
-
A.
numberOfRelocations
Indicates the total count of times an entity has been moved or relocated from one place or position to another.
-
B.
relocationMethod
chosen
Indicates the means or process by which something or someone is moved from one location to another.
-
C.
relocationAnnouncedBy
Indicates that the relocation of something (such as a person, organization, or asset) was publicly communicated or made known by a particular agent or source.
-
D.
hasMovementType
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
E.
relocationCompleted
Indicates that a previously initiated relocation process has been fully carried out and successfully finished.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.