Triple
T31176617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapri |
E794766
|
entity |
| Predicate | nearbyGulf |
P193892
|
FINISHED |
| Object | Gulf of Policastro |
E888908
|
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: Gulf of Policastro | Statement: [Sapri, nearbyGulf, Gulf of Policastro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyGulf Context triple: [Sapri, nearbyGulf, Gulf of Policastro]
-
A.
closestGulfState
Indicates that one state is geographically the nearest among all Gulf states to a given reference location or entity.
-
B.
nearbyStrait
Indicates that one entity is located close to or adjacent to a particular strait.
-
C.
hasGulf
Indicates that one geographic entity contains or is bordered by a gulf associated with another entity.
-
D.
nearbyGasField
Indicates that one entity is located close to a gas field associated with the other entity.
-
E.
nearbyCityOrPort
Indicates that one location is geographically close to a city or port, typically within a short travel distance.
- F. None of above. chosen
Provenance (5 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a29590ed890819089114960eba2f408 |
completed | June 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
| PDg | Predicate description generation | batch_69fd592cc56081908ce456114d407616 |
completed | May 8, 2026, 3:31 a.m. |
Created at: April 29, 2026, 9:08 p.m.