Triple
T29228036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyfall estate |
E740986
|
entity |
| Predicate | exteriorSetBuiltAt |
P166442
|
FINISHED |
| Object | Hankley Common, Surrey, England |
—
|
NE NERFINISHED |
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: Hankley Common, Surrey, England | Statement: [Skyfall estate, exteriorSetBuiltAt, Hankley Common, Surrey, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exteriorSetBuiltAt Context triple: [Skyfall estate, exteriorSetBuiltAt, Hankley Common, Surrey, England]
-
A.
yearBuilt
Indicates the specific year in which something (typically a structure or object) was constructed or completed.
-
B.
constructionDate
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
-
C.
exteriorMaterial
Indicates the material that forms the outer surface or outer construction of an object or structure.
-
D.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
E.
exteriorFeature
Indicates a relationship where one entity serves as an external or outward-facing feature, element, or characteristic 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66437bb6481908684a8453f6c4166 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 12:17 p.m.