Triple
T37002038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leaves Green |
E915377
|
entity |
| Predicate | locatedNearBoundaryOf |
P55118
|
FINISHED |
| Object | Kent |
E1582448
|
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: Kent | Statement: [Leaves Green, locatedNearBoundaryOf, Kent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearBoundaryOf Context triple: [Leaves Green, locatedNearBoundaryOf, Kent]
-
A.
hasNearbyBoundary
Indicates that one entity’s boundary lies close to, but does not necessarily touch or coincide with, the boundary of another entity.
-
B.
liesOnBorderOf
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
C.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
-
D.
nearBorderBetween
chosen
Indicates that something is located close to the dividing line or boundary shared between two adjacent areas or regions.
-
E.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
- F. None of above.
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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e576476b0819095c3d52b0b11e444 |
completed | June 26, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.