Triple
T37898218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Apsley |
E945337
|
entity |
| Predicate | hasConnectionWithBuilding |
P204463
|
FINISHED |
| Object | Apsley House |
E279408
|
NE 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: Apsley House | Statement: [Baron Apsley, hasConnectionWithBuilding, Apsley House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectionWithBuilding Context triple: [Baron Apsley, hasConnectionWithBuilding, Apsley House]
-
A.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
B.
belongsToBuilding
Indicates that one entity is part of, contained within, or assigned to a specific building.
-
C.
attachedBuilding
Indicates that one building is physically connected to or joined with another building as part of the same structural complex.
-
D.
hasNeighboringBuilding
Indicates that one building is located adjacent to or directly next to another building.
-
E.
belongsToBuildingComplex
Indicates that one building or structure is part of, or included within, a larger building complex.
- F. None of above. chosen
Provenance (5 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41710d5f088190be1b635b58a6092a |
completed | June 28, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:19 p.m.