Triple
T26208843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angel Road / Meridian Water area |
E655428
|
entity |
| Predicate | previousNameIncludes |
P65
|
FINISHED |
| Object | Angel Road |
—
|
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: Angel Road | Statement: [Angel Road / Meridian Water area, previousNameIncludes, Angel Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNameIncludes Context triple: [Angel Road / Meridian Water area, previousNameIncludes, Angel Road]
-
A.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
B.
previousNamePeriod
Indicates the time span during which an entity was known by a former name before changing to its current name.
-
C.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
-
D.
containsFormerlyNamed
Indicates that one entity currently contains another entity that was previously known by a different name.
-
E.
previousNameOfDate
Indicates that one date was formerly known or designated by another date, representing a prior naming or labeling of the same temporal reference.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 26, 2026, 8:51 p.m.