Triple
T32928934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recorder of Newcastle |
E842346
|
entity |
| Predicate | isHistoricalOffice |
P47924
|
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: [Recorder of Newcastle, isHistoricalOffice, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricalOffice Context triple: [Recorder of Newcastle, isHistoricalOffice, true]
-
A.
isHistoricOffice
chosen
Indicates that an office or position has historical significance, typically due to its age, legacy, or role in past events.
-
B.
hasHistoricalOfficeHolder
Indicates that an office, position, or role has been held by a specific person at some point in the past.
-
C.
hasHeldOfficeType
Indicates that an entity has at some time occupied or served in a specified type or category of office or position.
-
D.
hasHistoricalRoleAs
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
-
E.
isPoliticalOffice
Indicates that the subject is a formal governmental or political position held within a public institution or authority.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d0dbd5108190a3f47d397a2b3f63 |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.