Triple
T15671548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuiderzee Works |
E377322
|
entity |
| Predicate | createdSettlement |
P89920
|
FINISHED |
| Object | Lelystad |
—
|
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: Lelystad | Statement: [Zuiderzee Works, createdSettlement, Lelystad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdSettlement Context triple: [Zuiderzee Works, createdSettlement, Lelystad]
-
A.
organizedSettlement
chosen
Indicates that an entity actively planned, coordinated, and arranged the establishment or occurrence of a settlement.
-
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.
coveredSettlementWith
Indicates that one entity (such as a material or structure) physically covers or overlays a settlement.
-
D.
otherSettlement
Indicates that one settlement is another, different settlement distinct from the primary or reference settlement.
-
E.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f13b1b08190beabc9f4098aa096 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.