Triple
T25074220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Adriatic region |
E628002
|
entity |
| Predicate | sharesMaritimeHeritageWith |
P162561
|
FINISHED |
| Object | Slovenia |
E18381
|
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: Slovenia | Statement: [Northern Adriatic region, sharesMaritimeHeritageWith, Slovenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesMaritimeHeritageWith Context triple: [Northern Adriatic region, sharesMaritimeHeritageWith, Slovenia]
-
A.
sharesMaritimeHeritageWith
chosen
Indicates that two entities have a common maritime history, traditions, or seafaring cultural background.
-
B.
hasMaritimeHeritage
Indicates that an entity possesses a historical, cultural, or traditional connection to maritime activities, seafaring, or the sea.
-
C.
hasMaritimeMuseum
Indicates that one entity possesses, hosts, or includes a maritime museum as part of its features or facilities.
-
D.
shareMaritimeAgreements
Indicates that two or more entities are parties to the same maritime-related agreements, such as treaties, conventions, or cooperative arrangements governing activities at sea.
-
E.
seaVoyages
Indicates that one entity undertakes or is associated with journeys or travel by sea to or involving 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1075bb30d48190bb61d4f909b263d3 |
completed | May 22, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 6:20 a.m.