Triple
T2144016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Ambulance Service |
E47022
|
entity |
| Predicate | reorganizedAsDate |
P5212
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [London Ambulance Service, reorganizedAsDate, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reorganizedAsDate Context triple: [London Ambulance Service, reorganizedAsDate, 1990s]
-
A.
reformDate
chosen
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
-
B.
reorganizedAs
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
-
C.
reorganizedIn
Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
-
D.
reenvisionedDate
Indicates the date on which something was newly reimagined, redesigned, or conceptually revised.
-
E.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.