Triple
T15919963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seward's Folly |
E386064
|
entity |
| Predicate | nowViewedAs |
P102849
|
FINISHED |
| Object | misleading characterization of Alaska Purchase |
—
|
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: misleading characterization of Alaska Purchase | Statement: [Seward's Folly, nowViewedAs, misleading characterization of Alaska Purchase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nowViewedAs Context triple: [Seward's Folly, nowViewedAs, misleading characterization of Alaska Purchase]
-
A.
viewsAs
chosen
Indicates that one entity perceives, interprets, or regards another entity in a particular way or role.
-
B.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
C.
viewedBy
Indicates that something has been seen, observed, or watched by a particular entity.
-
D.
viewedHistoryAs
Indicates that one entity has examined or interpreted another entity as a historical record or in the context of its past events.
-
E.
viewsClientAs
Indicates that one entity regards or treats another entity as a client within a service, business, or professional relationship.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.