Triple
T28748914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ria da Coruña |
E731460
|
entity |
| Predicate | maritimeSettingOf |
P44766
|
FINISHED |
| Object | A Coruña |
—
|
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: A Coruña | Statement: [Ria da Coruña, maritimeSettingOf, A Coruña]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeSettingOf Context triple: [Ria da Coruña, maritimeSettingOf, A Coruña]
-
A.
maritimeSettingFor
chosen
Indicates that one entity serves as the maritime or ocean-related environment or backdrop in which another entity is situated or occurs.
-
B.
locatedAtSea
Indicates that something exists or is situated in or on the sea.
-
C.
maritimeUsage
Indicates the extent to which something is used for or involved in maritime activities, such as sea transport, navigation, or ocean-related operations.
-
D.
maritimeActivity
Indicates activities, operations, or behaviors that take place at sea or are directly related to maritime environments and navigation.
-
E.
usesAtSea
Indicates that something is employed, operated, or applied in a maritime or oceanic environment.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:06 a.m.