Triple
T32617259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drakonera |
E833820
|
entity |
| Predicate | locatedInRegionalSea |
P179115
|
FINISHED |
| Object | Mediterranean Sea |
E1489
|
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: Mediterranean Sea | Statement: [Drakonera, locatedInRegionalSea, Mediterranean Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInRegionalSea Context triple: [Drakonera, locatedInRegionalSea, Mediterranean Sea]
-
A.
locatedInSeaBasin
Indicates that something is situated within or belongs to a particular sea basin.
-
B.
isInSeaRegion
chosen
Indicates that one entity (typically a location or object) is situated within the boundaries of a specified sea region.
-
C.
isMaritimeRegion
Indicates that a region is primarily associated with the sea or ocean, such as being coastal, oceanic, or otherwise defined by maritime characteristics or activities.
-
D.
locatedAtSea
Indicates that something exists or is situated in or on the sea.
-
E.
isPartOfSea
Indicates that one entity is a portion, region, or component contained within a larger sea.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a030713bd2881908bcc69e7d1e9fd09 |
completed | May 12, 2026, 10:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3485f7cdc88190b653f8a7e286a4f1 |
completed | June 18, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_6a0304c29abc819085ffd17ab9a8c844 |
completed | May 12, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:06 a.m.