Triple
T20824192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ertholmene |
E512653
|
entity |
| Predicate | hasBuildingRestriction |
P96226
|
FINISHED |
| Object | no new buildings without special permission |
—
|
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: no new buildings without special permission | Statement: [Ertholmene, hasBuildingRestriction, no new buildings without special permission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingRestriction Context triple: [Ertholmene, hasBuildingRestriction, no new buildings without special permission]
-
A.
hasZoningRestriction
chosen
Indicates that an entity is subject to a specific zoning-related limitation or regulatory constraint.
-
B.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
C.
hasResidentialBuilding
Indicates that an entity possesses, contains, or is associated with a residential building as part of its properties or components.
-
D.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
E.
movementRestrictions
Indicates limitations, rules, or prohibitions that constrain how, where, or when an entity is allowed to move.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2fcc60881908ef3d8914d801ea1 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.