Triple
T31838851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Wilson |
E812745
|
entity |
| Predicate | houseLocationRelativeToDennis |
P59923
|
FINISHED |
| Object | next door |
—
|
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: next door | Statement: [George Wilson, houseLocationRelativeToDennis, next door]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseLocationRelativeToDennis Context triple: [George Wilson, houseLocationRelativeToDennis, next door]
-
A.
positionRelativeToBuilding
chosen
Indicates the spatial relationship of an entity’s location with respect to a specific building (e.g., in front of, behind, adjacent to, on top of).
-
B.
doorLocation
Indicates the spatial position or placement of a door relative to a reference structure or area.
-
C.
homeStandLocation
Indicates the location where the home team’s primary stand or seating area is situated.
-
D.
relativeLocationOnIsland
Indicates a spatial relationship where one entity’s position is described relative to another entity specifically in the context of being on an island.
-
E.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 30, 2026, 11:48 p.m.