Triple
T4891374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frentani |
E109569
|
entity |
| Predicate | coastalExtent |
P8868
|
FINISHED |
| Object | between the rivers Tifernus and Aternus |
—
|
LITERAL 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: between the rivers Tifernus and Aternus | Statement: [Frentani, coastalExtent, between the rivers Tifernus and Aternus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalExtent Context triple: [Frentani, coastalExtent, between the rivers Tifernus and Aternus]
-
A.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
B.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
-
C.
influencedCoastlineOf
Indicates that one entity has affected, shaped, or altered the characteristics, form, or condition of another entity’s coastline.
-
D.
coastlineFeature
Indicates that a geographic entity is a specific type of feature located along or forming part of a coastline.
-
E.
territorialExtent
chosen
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffabccc81909115ece1b04e2061 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2e7b5c8190b8bf9d616dfa24f0 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:28 p.m.