Triple
T35870599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Greenland |
E1037211
|
entity |
| Predicate | wasSettledBy |
P183926
|
FINISHED |
| Object | Norse |
—
|
NE NERFINISHED |
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: Norse | Statement: [Southern Greenland, wasSettledBy, Norse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSettledBy Context triple: [Southern Greenland, wasSettledBy, Norse]
-
A.
settledAs
Indicates that one entity has been resolved, finalized, or agreed upon in the form or status of another entity.
-
B.
settlementWith
Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
-
C.
reachedSettlement
Indicates that the involved parties have come to a mutually agreed resolution of a dispute or claim, typically avoiding further legal or formal proceedings.
-
D.
isSettlementOf
Indicates that one entity is a settlement (such as a town, village, or city) that belongs to, is located within, or is administratively part of another entity.
-
E.
settlementApprovedBy
Indicates that a proposed settlement has received formal approval or authorization from a specified person, group, or authority.
- F. None of above. chosen
Provenance (4 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa33e0488190a135166bb67e1118 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.