Triple
T23279373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pons Aelius |
E588814
|
entity |
| Predicate | originalFunctionForCity |
P93343
|
FINISHED |
| Object | military and urban nucleus of Newcastle upon Tyne |
—
|
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: military and urban nucleus of Newcastle upon Tyne | Statement: [Pons Aelius, originalFunctionForCity, military and urban nucleus of Newcastle upon Tyne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalFunctionForCity Context triple: [Pons Aelius, originalFunctionForCity, military and urban nucleus of Newcastle upon Tyne]
-
A.
cityFunction
chosen
Indicates the primary role, purpose, or functional classification associated with a city (e.g., administrative, commercial, industrial, cultural).
-
B.
otherCity
Indicates that one city is different from and not the same as another city.
-
C.
formerBaseCity
Indicates that a location previously served as the primary base or home city for an entity, but no longer holds that status.
-
D.
operatorCity
Indicates the city in which an operator is based or primarily operates.
-
E.
cityDerivation
Indicates that one city is derived from, created out of, or established as a successor to another city.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196419eac819081d0beb5767046dc |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:50 p.m.