Triple
T34694709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newcastle upon Tyne East |
E890993
|
entity |
| Predicate | previouslyExistedFrom |
P192911
|
FINISHED |
| Object | 1918 |
—
|
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: 1918 | Statement: [Newcastle upon Tyne East, previouslyExistedFrom, 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyExistedFrom Context triple: [Newcastle upon Tyne East, previouslyExistedFrom, 1918]
-
A.
previousExistence
chosen
Indicates that one entity existed at an earlier time or state relative to another, or prior to a specified reference point.
-
B.
existedAs
Indicates that one entity had the status, form, or identity of another entity during a certain time or context.
-
C.
existedAfter
Indicates that one entity came into existence only after another entity already existed.
-
D.
previouslyContained
Indicates that one entity was contained within another entity at some point in the past, but is not necessarily contained there now.
-
E.
previouslyEstablished
Indicates that the relationship or condition it connects has already been formed or confirmed at an earlier time before the current context.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: May 1, 2026, 2:05 a.m.