Triple
T30222855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Dixon |
E768395
|
entity |
| Predicate | notableVoyageDestination |
P35273
|
FINISHED |
| Object | Alaska coast |
E1295659
|
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: Alaska coast | Statement: [George Dixon, notableVoyageDestination, Alaska coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVoyageDestination Context triple: [George Dixon, notableVoyageDestination, Alaska coast]
-
A.
notableDestination
chosen
Indicates that a location is recognized as a significant or prominent place that people commonly travel to or aim to visit.
-
B.
notableDestinationType
Indicates the general category or type of destination for which something is considered notable.
-
C.
notableDiasporaDestination
Indicates that a place is a significant destination or center for the diaspora of a particular group or population.
-
D.
notableExpeditionLocation
Indicates that a location is a significant or primary place associated with a particular expedition.
-
E.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27643f0a40819087c0ff9e1997d6a2 |
completed | June 9, 2026, 12:54 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:35 p.m.