Triple
T20630751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holland House ruins |
E506945
|
entity |
| Predicate | survivingFunction |
P140839
|
FINISHED |
| Object | scenic backdrop |
—
|
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: scenic backdrop | Statement: [Holland House ruins, survivingFunction, scenic backdrop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingFunction Context triple: [Holland House ruins, survivingFunction, scenic backdrop]
-
A.
survivorsFunction
Indicates that an entity serves or served in a particular functional role or capacity as a survivor in relation to an event or circumstance.
-
B.
survivalFunction
Indicates the probability that an entity or system continues to exist or function without failure beyond a given point in time.
-
C.
survivesBy
Indicates that one entity continues to live or exist after another entity has died or ceased to exist.
-
D.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
E.
survivesFor
Indicates that one entity continues to exist, endure, or remain functional for a specified duration or period.
- F. None of above. chosen
Provenance (4 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad09c71881909698d3c2576cc181 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.