Triple
T30687056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parlington estate |
E781213
|
entity |
| Predicate | currentFeatureStatus |
P100613
|
FINISHED |
| Object | house largely demolished |
—
|
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: house largely demolished | Statement: [Parlington estate, currentFeatureStatus, house largely demolished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentFeatureStatus Context triple: [Parlington estate, currentFeatureStatus, house largely demolished]
-
A.
currentFeature
Indicates that an entity is the feature or functionality that is presently active, selected, or in focus within a given context.
-
B.
actualStatus
Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
-
C.
hasFeatureStatus
chosen
Indicates that an entity possesses a particular feature along with its current state or condition.
-
D.
runtimeStatus
Indicates the current operational state or condition of an entity while it is running or executing.
-
E.
modernStatus
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 29, 2026, 8:33 p.m.