Triple
T35895912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parthenius River |
E1038222
|
entity |
| Predicate | formedBoundaryOf |
P71578
|
FINISHED |
| Object | Paphlagonia |
—
|
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: Paphlagonia | Statement: [Parthenius River, formedBoundaryOf, Paphlagonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedBoundaryOf Context triple: [Parthenius River, formedBoundaryOf, Paphlagonia]
-
A.
formsBoundaryType
Indicates that one entity serves as a specific type of boundary for another entity.
-
B.
isBoundaryFor
chosen
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
C.
outerBoundary
Indicates that one entity serves as the enclosing outer limit or perimeter that bounds another entity or region.
-
D.
boundaryCurrentOf
Indicates that one entity represents the current or present form/state of a boundary that is associated with or derived from another entity.
-
E.
isPartOfLargerBoundary
Indicates that one boundary is contained within or forms a component of a larger encompassing boundary.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00781b749c8190921c46e110cae0b0 |
completed | May 10, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_6a0077df3c8481909fabc9e84f5936e3 |
completed | May 10, 2026, 12:19 p.m. |
Created at: May 3, 2026, 4:06 p.m.