Triple
T36983730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parque de Bombas |
E914904
|
entity |
| Predicate | usedAsFireStationUntil |
P198507
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Parque de Bombas, usedAsFireStationUntil, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsFireStationUntil Context triple: [Parque de Bombas, usedAsFireStationUntil, 1989]
-
A.
usedAsCityHallUntil
Indicates that a building or location functioned as the city hall up to a specified end date or time period.
-
B.
buildingUsedSince
Indicates that a particular building has been in use starting from a specified point in time.
-
C.
usedAsCityHallFrom
Indicates that a building or location functioned as the official city hall of a municipality during a specified time period.
-
D.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
E.
predecessorBuildingFireYear
Indicates that the referenced year is when a fire occurred in a building that preceded or was replaced by the current building.
- F. None of above. chosen
Provenance (4 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69feecf102e08190b237c29e45beeca0 |
completed | May 9, 2026, 8:14 a.m. |
Created at: May 3, 2026, 4:14 p.m.