Triple
T30222797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Boundary Tribunal of 1903 |
E768394
|
entity |
| Predicate | hasUSMember |
P169375
|
FINISHED |
| Object | Elihu Root |
—
|
NE NERFINISHED |
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: Elihu Root | Statement: [Alaska Boundary Tribunal of 1903, hasUSMember, Elihu Root]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUSMember Context triple: [Alaska Boundary Tribunal of 1903, hasUSMember, Elihu Root]
-
A.
hasUSAN
Indicates that an entity has a specified United States Adopted Name (USAN), typically a nonproprietary name assigned to a pharmaceutical substance.
-
B.
memberStatesAreMemberOf
Indicates that certain states belong to or hold membership in a particular organization, group, or union.
-
C.
NATOMembershipOfUnitedStates
Indicates that the United States holds membership status in the NATO military alliance.
-
D.
isInUnitedStates
Indicates that one entity is located within the geographic or political boundaries of the United States.
-
E.
hasNetworkUS
Indicates that an entity possesses, operates, or is associated with a network located in or serving the United States.
- F. None of above. chosen
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_69f6801e5eb081908d07ef701d78118b |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:35 p.m.