Triple
T567544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor of Alaska |
E13587
|
entity |
| Predicate | createdFollowing |
P9059
|
FINISHED |
| Object | Alaska statehood |
—
|
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: Alaska statehood | Statement: [Governor of Alaska, createdFollowing, Alaska statehood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdFollowing Context triple: [Governor of Alaska, createdFollowing, Alaska statehood]
-
A.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
B.
establishedFollowing
chosen
Indicates that one entity created or set up another entity after, and in consequence of, a prior entity or event.
-
C.
followsWork
Indicates that one work (such as a publication, version, or creative piece) comes directly after another in sequence or succession.
-
D.
layFollowers
Indicates that one entity is a non-ordained (lay) follower or adherent of another entity, typically a religious figure, institution, or tradition.
-
E.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b02da148190b6a9bad3a22d8ec5 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c183b081909304944aa3d0fe8f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.