Triple
T27822970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederiksnagore |
E702871
|
entity |
| Predicate | establishedAsDanishSettlement |
P174262
|
FINISHED |
| Object | 1755 |
—
|
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: 1755 | Statement: [Frederiksnagore, establishedAsDanishSettlement, 1755]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsDanishSettlement Context triple: [Frederiksnagore, establishedAsDanishSettlement, 1755]
-
A.
foundedAsSettlementFor
Indicates that one entity was originally established specifically to serve as a settlement for another entity (such as a group, population, or community).
-
B.
locatedInSettlementFoundedBy
Indicates that something is located in a settlement that was founded by a specified entity.
-
C.
originOfSettlement
Indicates the place, source, or starting point from which a settlement was established or originated.
-
D.
foundedAsModernSettlement
Indicates that one entity was established or created as a modern-era settlement, rather than originating as an ancient or historical habitation.
-
E.
secondSettlementFounded
Indicates that an entity established its second settlement at a particular place and/or time.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 27, 2026, 5:49 p.m.