Triple
T1870682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherokee Nation v. Georgia |
E39027
|
entity |
| Predicate | partyTypeCharacterization |
P6384
|
FINISHED |
| Object | ward of the United States |
—
|
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: ward of the United States | Statement: [Cherokee Nation v. Georgia, partyTypeCharacterization, ward of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyTypeCharacterization Context triple: [Cherokee Nation v. Georgia, partyTypeCharacterization, ward of the United States]
-
A.
typicalParty
Indicates that an entity is a usual, standard, or characteristic participant in a given type of event, situation, or relationship.
-
B.
party
Indicates that an entity participates as a side or participant in an event, agreement, or situation.
-
C.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
D.
typeOfEvent
Indicates that one entity is classified as a specific kind or category of event.
-
E.
speakerParty
Indicates the political party or group affiliation of the entity acting as the speaker in a given context.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0f79fbc819085c54f3189a552d9 |
completed | March 7, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69abafe2b56c81909e13d543982e6e13 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.