Triple
T24321149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glendevon |
E612965
|
entity |
| Predicate | locatedInGlen |
P40
|
FINISHED |
| Object | Glendevon Glen |
—
|
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: Glendevon Glen | Statement: [Glendevon, locatedInGlen, Glendevon Glen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInGlen Context triple: [Glendevon, locatedInGlen, Glendevon Glen]
-
A.
locatedInNorthernSuburbOf
Indicates that one entity is situated within the northern suburban area relative to another reference location.
-
B.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
D.
locatedOnLoop
Indicates that an entity is situated along or directly on a loop-shaped path, route, or circuit.
-
E.
locatedInRegionalDistrict
Indicates that one entity is geographically situated within the boundaries of a specified regional district.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ab2fa08190bc19c3edc0a1a9b2 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:51 a.m.