Triple
T32928923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recorder of Newcastle |
E842346
|
entity |
| Predicate | isMunicipalOffice |
P119705
|
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, isMunicipalOffice, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMunicipalOffice Context triple: [Recorder of Newcastle, isMunicipalOffice, true]
-
A.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
B.
isMunicipalAgency
chosen
Indicates that an entity functions as an agency or department of a municipal (city or local) government.
-
C.
isMunicipalStatus
Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
-
D.
hasLocalGovernmentOffice
Indicates that a local government office is present or established within a specified location or jurisdiction.
-
E.
isLocalGovernment
Indicates that an entity functions as a governing body with authority over a specific local or regional area within a larger political system.
- 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_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:20 a.m.