Triple
T19561045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarence Island ice cap |
E489449
|
entity |
| Predicate | hasRunoffDestination |
P83648
|
FINISHED |
| Object | surrounding seas |
—
|
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: surrounding seas | Statement: [Clarence Island ice cap, hasRunoffDestination, surrounding seas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunoffDestination Context triple: [Clarence Island ice cap, hasRunoffDestination, surrounding seas]
-
A.
hasRunoffDirection
Indicates the direction in which runoff (such as water or other liquid) flows or is directed from a given source or surface.
-
B.
hasRunoffAreas
Indicates that an entity includes or is equipped with designated runoff areas for managing excess water or liquid flow.
-
C.
runoffElectionDay
Indicates the day on which a runoff election is held to determine a winner when no candidate achieved the required threshold in a prior election.
-
D.
hasDestinationRegion
chosen
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
-
E.
flownToIndicate
Indicates that one entity has traveled by air to reach or visit another entity or location.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f7442e08190ad030151ec0a97d4 |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.