Triple
T36065238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northgate Street |
E1043206
|
entity |
| Predicate | usedToBeNameOf |
P65
|
FINISHED |
| Object | a central shopping thoroughfare in Oxford |
—
|
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: a central shopping thoroughfare in Oxford | Statement: [Northgate Street, usedToBeNameOf, a central shopping thoroughfare in Oxford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToBeNameOf Context triple: [Northgate Street, usedToBeNameOf, a central shopping thoroughfare in Oxford]
-
A.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
B.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
-
C.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
D.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
E.
usedToBeSameAs
Indicates that two entities were identical or represented the same thing at some point in the past, but no longer do.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.