Triple
T35315837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livorno |
E1019901
|
entity |
| Predicate | hasNeighboringSettlementInDistrict |
P201610
|
FINISHED |
| Object | Lelydorp |
—
|
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: Lelydorp | Statement: [Livorno, hasNeighboringSettlementInDistrict, Lelydorp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringSettlementInDistrict Context triple: [Livorno, hasNeighboringSettlementInDistrict, Lelydorp]
-
A.
hasAdjacentSettlement
Indicates that one settlement is located directly next to or bordering another settlement.
-
B.
hasNeighbouringEstate
Indicates that one estate is directly adjacent to or shares a boundary with another estate.
-
C.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
-
D.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
-
E.
hasNeighboringChiefdom
Indicates that one chiefdom is geographically adjacent to or directly borders another chiefdom.
- F. None of above. chosen
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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_6a000be4d3f48190bdecd0a044a0e453 |
completed | May 10, 2026, 4:39 a.m. |
Created at: May 3, 2026, 4:03 p.m.