Triple
T28013657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lost Gardens of Heligan |
E707486
|
entity |
| Predicate | fellIntoNeglect |
P163623
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [The Lost Gardens of Heligan, fellIntoNeglect, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fellIntoNeglect Context triple: [The Lost Gardens of Heligan, fellIntoNeglect, 20th century]
-
A.
neglects
Indicates a relationship where one party fails to give appropriate attention, care, or consideration to another party or responsibility.
-
B.
fellInto
Indicates that one entity moved downward, unintentionally or uncontrollably, and ended up inside or within another entity or space.
-
C.
fell
Indicates that an entity moved downward from a higher position to a lower one, typically due to gravity, often unintentionally or uncontrollably.
-
D.
fellFromFavorUnder
Indicates that an entity lost approval, status, or support while another specified party was in power or in a position of authority.
-
E.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c05d4748190bf9bda3c4113636e |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:05 p.m.