Triple
T26019086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reigersbos |
E647106
|
entity |
| Predicate | fireServiceDistrict |
P62810
|
FINISHED |
| Object | Amsterdam-Amstelland |
—
|
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-Amstelland | Statement: [Reigersbos, fireServiceDistrict, Amsterdam-Amstelland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireServiceDistrict Context triple: [Reigersbos, fireServiceDistrict, Amsterdam-Amstelland]
-
A.
fireJurisdiction
Indicates that one entity has official authority and responsibility over fire protection, prevention, or response activities within the area or domain of another entity.
-
B.
fireRescue
Indicates a relationship where one entity performs or is responsible for rescuing people or property from fires or fire-related emergencies involving another entity.
-
C.
fireServiceBy
Indicates that a fire protection or firefighting service is provided, operated, or carried out by a specified agent or organization.
-
D.
hasFireServicesFrom
chosen
Indicates that one entity receives fire protection or firefighting services from another entity.
-
E.
hasFireRescueService
Indicates that an entity is served by, or responsible for providing, a fire and rescue service.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605bbb17c819080f6b026c2cbc186 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:03 a.m.