Triple
T25577803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lock 22 |
E641157
|
entity |
| Predicate | locatedAtSettlement |
P44412
|
FINISHED |
| Object | Merrickville |
—
|
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: Merrickville | Statement: [Lock 22, locatedAtSettlement, Merrickville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtSettlement Context triple: [Lock 22, locatedAtSettlement, Merrickville]
-
A.
isLocatedInSettlement
chosen
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
-
B.
mainSettlementLocatedOn
Indicates that the primary settlement of an area is situated on or directly adjacent to a specified geographic feature or location.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
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).
-
E.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 21, 2026, 4:02 p.m.