Triple
T36993517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wûnseradiel |
E915166
|
entity |
| Predicate | hadNotableVillage |
P4011
|
FINISHED |
| Object | Makkum, known for pottery and shipbuilding |
—
|
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: Makkum, known for pottery and shipbuilding | Statement: [Wûnseradiel, hadNotableVillage, Makkum, known for pottery and shipbuilding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNotableVillage Context triple: [Wûnseradiel, hadNotableVillage, Makkum, known for pottery and shipbuilding]
-
A.
hasNotableTown
Indicates that an entity includes or is associated with a town that is considered notable or significant in some way.
-
B.
hasVillage
chosen
Indicates that an entity possesses, contains, or is associated with a village.
-
C.
hasPopularVillage
Indicates that an entity is associated with or contains a village that is widely known, well-liked, or frequently visited.
-
D.
hadNoSignificantUrbanSettlementBy
Indicates that a given place did not possess any major or notable urban settlement up to and including the specified time.
-
E.
hasNotablePortTown
Indicates that an entity possesses or is associated with a town known for its significant or prominent port.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.