Triple
T28804295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peucetians |
E727329
|
entity |
| Predicate | areaBorderedBy |
P10768
|
FINISHED |
| Object | Adriatic Sea |
—
|
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: Adriatic Sea | Statement: [Peucetians, areaBorderedBy, Adriatic Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaBorderedBy Context triple: [Peucetians, areaBorderedBy, Adriatic Sea]
-
A.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
B.
areaDefinedAs
Indicates that one area is formally specified, delimited, or characterized in terms of another area or defining criteria.
-
C.
areaApprox
Indicates that one entity’s area is approximately equal to the area of another entity.
-
D.
enclosesArea
Indicates that one entity surrounds and contains a bounded region of space occupied or defined by another.
-
E.
borderRegionOf
chosen
Indicates that one region lies along, touches, or forms part of the boundary of another region.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:28 a.m.