Triple
T3680428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M/V Kennicott |
E78096
|
entity |
| Predicate | callsAt |
P42455
|
FINISHED |
| Object | Southeast Alaska communities |
—
|
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: Southeast Alaska communities | Statement: [M/V Kennicott, callsAt, Southeast Alaska communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callsAt Context triple: [M/V Kennicott, callsAt, Southeast Alaska communities]
-
A.
callsFor
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
-
B.
nowCalled
Indicates that an entity previously known by one name is currently referred to by a different name.
-
C.
callingPoint
chosen
Indicates that one entity serves as a stop, station, or intermediate point that another entity (such as a route, journey, or service) calls at or passes through.
-
D.
callType
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
-
E.
calledAs
Indicates that one entity is referred to, named, or addressed by another specific name or label.
- 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc49153ec81909ff3a3df54416d0e |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.