Triple
T20824193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ertholmene |
E512653
|
entity |
| Predicate | hasCarRestriction |
P33452
|
FINISHED |
| Object | no private cars |
—
|
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 private cars | Statement: [Ertholmene, hasCarRestriction, no private cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarRestriction Context triple: [Ertholmene, hasCarRestriction, no private cars]
-
A.
hasLimitedRoadAccess
Indicates that an entity can only be reached by a small number of roads, restricted routes, or otherwise constrained vehicular access.
-
B.
rideRestriction
Indicates that there is a limitation or rule governing whether, how, or under what conditions one entity may ride or be transported by another.
-
C.
hasSpeedRestriction
Indicates that an entity is subject to a specified limit on its allowable speed.
-
D.
transportRestriction
chosen
Indicates that there are limitations, prohibitions, or special conditions governing the use of a particular mode or means of transportation between entities.
-
E.
hasSpeedRestrictionReason
Indicates the reason or cause for which a speed restriction has been imposed on an entity.
- 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.