Triple
T20075111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davis Inlet |
E499840
|
entity |
| Predicate | peopleMovedTo |
P100317
|
FINISHED |
| Object | planned community of Natuashish |
—
|
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: planned community of Natuashish | Statement: [Davis Inlet, peopleMovedTo, planned community of Natuashish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peopleMovedTo Context triple: [Davis Inlet, peopleMovedTo, planned community of Natuashish]
-
A.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
B.
cityAfterRelocation
chosen
Indicates the city where an entity is located after it has been moved or relocated from a previous place.
-
C.
movedCommunityTo
Indicates that an entity caused a community or group to relocate from one place to another.
-
D.
capitalMovedFrom
Indicates that a capital city was relocated from one place (the source) to another (the destination).
-
E.
influencedRelocationOf
Indicates that one entity played a causal or motivating role in another entity’s decision or action to move from one location to another.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643ab0448190ab18d013b72aaf32 |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.