Triple
T29452654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Party (Cherokee) |
E747016
|
entity |
| Predicate | positionOnRemoval |
P194897
|
FINISHED |
| Object | supported removal to Indian Territory |
—
|
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: supported removal to Indian Territory | Statement: [National Party (Cherokee), positionOnRemoval, supported removal to Indian Territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnRemoval Context triple: [National Party (Cherokee), positionOnRemoval, supported removal to Indian Territory]
-
A.
afterRemoval
Indicates that a condition, state, or relationship holds only once a specified entity or element has been removed.
-
B.
positionOnReduction
Indicates the stance or viewpoint an entity holds regarding the reduction or decrease of something (e.g., size, amount, scope, or intensity).
-
C.
positionOnRelease
Indicates the spatial position or location of an entity at the moment it is released.
-
D.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
positionOnDeath
Indicates the role, title, or position an entity held at the time of its death.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
| PDg | Predicate description generation | batch_69fd8e5e9ca48190890a2caddc1f9f5c |
completed | May 8, 2026, 7:18 a.m. |
Created at: April 28, 2026, 3:34 p.m.