Triple
T2869086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Heritage List for England entry |
E63512
|
entity |
| Predicate | recordsStatus |
P4082
|
FINISHED |
| Object | current designation status |
—
|
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: current designation status | Statement: [National Heritage List for England entry, recordsStatus, current designation status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsStatus Context triple: [National Heritage List for England entry, recordsStatus, current designation status]
-
A.
historicalRecordStatus
chosen
Indicates the status or condition of a record within a historical or archival context (e.g., active, archived, revised, or obsolete).
-
B.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
C.
recordHeldIn
Indicates that a record is stored, maintained, or kept within a particular location, system, or repository.
-
D.
recordHeldFrom
Indicates that a record or position was held by an entity starting from a specified point in time.
-
E.
reconstructionStatus
Indicates the current state or phase of a reconstruction process that an entity is undergoing or has undergone.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfdfef1881909dc52a1b34cd24e3 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.