Triple
T32900735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barentszplein |
E841601
|
entity |
| Predicate | isNamedPublicSpaceIn |
P142826
|
FINISHED |
| Object | Amsterdam |
—
|
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: Amsterdam | Statement: [Barentszplein, isNamedPublicSpaceIn, Amsterdam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedPublicSpaceIn Context triple: [Barentszplein, isNamedPublicSpaceIn, Amsterdam]
-
A.
isNamedPublicSpaceOf
chosen
Indicates that a public space (such as a park, square, or street) bears the name associated with a particular entity (such as a person, event, or organization).
-
B.
isInPublicSpace
Indicates that an entity is located within a space that is publicly accessible or open to the general public.
-
C.
isMajorPublicSpaceOf
Indicates that a location functions as a primary, widely accessible public area within or associated with another place or entity.
-
D.
hasPublicSpaceAlong
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
-
E.
hasPublicSpaceRole
Indicates that an entity holds a specific role, function, or responsibility within a public space.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:19 a.m.