Triple
T15565030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gavrio |
E371092
|
entity |
| Predicate | roleInIsland |
P106416
|
FINISHED |
| Object | main arrival point for goods |
—
|
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: main arrival point for goods | Statement: [Gavrio, roleInIsland, main arrival point for goods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInIsland Context triple: [Gavrio, roleInIsland, main arrival point for goods]
-
A.
roleOnIsland
chosen
Indicates the specific function, position, or responsibility an entity holds within the context of an island.
-
B.
roleAtSavoIsland
Indicates the specific role, position, or function an entity held in relation to the event or context associated with Savo Island.
-
C.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
D.
roleInExpedition
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
E.
roleInCoco
Indicates that an entity serves a specific role or function within the context of the COCO dataset or framework.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ddd753c8190b51eaef433258081 |
completed | April 16, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:10 a.m.