Triple
T6231889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckingham College |
E139373
|
entity |
| Predicate | isHistoricName |
P66486
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Buckingham College, isHistoricName, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricName Context triple: [Buckingham College, isHistoricName, true]
-
A.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
B.
hasHistoricNameVariant
chosen
Indicates that an entity has an alternative name that was used in a historical period or past context.
-
C.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
D.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
-
E.
hasHistoricalOrigin
Indicates that something originated, was first established, or came into existence during a specific historical period or 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062ee6f088190bf72692eb8ffb761 |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.