Triple
T32319124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe/Brussels |
E825723
|
entity |
| Predicate | historicalTimeChanges |
P12951
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Europe/Brussels, historicalTimeChanges, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTimeChanges Context triple: [Europe/Brussels, historicalTimeChanges, true]
-
A.
historicalOffsetChanges
chosen
Indicates that the relationship captures past changes in an offset value between entities, including when and how that offset was modified over time.
-
B.
historicalZone
Indicates that a location is designated as a historically significant area or district, often due to its cultural, architectural, or historical importance.
-
C.
historicalUtcOffsetChangeYear
Indicates the year in which the UTC offset for a given entity (such as a time zone or region) changed from its previous value.
-
D.
changesTimeline
Indicates that one entity alters, restructures, or otherwise affects the sequence or scheduling of events associated with another entity.
-
E.
historicalModification
Indicates that one entity has altered, updated, or otherwise changed another entity at some point in the past, with the modification recorded as part of its history.
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
Created at: May 1, 2026, 12:46 a.m.