Triple
T18927757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanisivik |
E463017
|
entity |
| Predicate | settlementAbandoned |
P28740
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Nanisivik, settlementAbandoned, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settlementAbandoned Context triple: [Nanisivik, settlementAbandoned, early 2000s]
-
A.
lostSettlement
Indicates that a settlement previously possessed by an entity has been relinquished or is no longer under that entity’s control.
-
B.
abandonedBefore
Indicates that one entity ceased or gave up on something prior in time to another entity doing so.
-
C.
abandonedDuring
Indicates that one entity ceased support for or deserted another entity in the midst of an ongoing process, event, or period.
-
D.
settlementWith
Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
-
E.
abandonedBy
chosen
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9bdddb481908bebd32f927ed5de |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.