Triple
T793256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uncas |
E16960
|
entity |
| Predicate | playedRole |
P3512
|
FINISHED |
| Object | power balance among southern New England tribes |
—
|
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: power balance among southern New England tribes | Statement: [Uncas, playedRole, power balance among southern New England tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedRole Context triple: [Uncas, playedRole, power balance among southern New England tribes]
-
A.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
B.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
playedKeyRoleIn
chosen
Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
-
D.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
-
E.
portrayedBy
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79a3bbc81908d818c50a366b0f8 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a510f61881909175d6d8719246cd |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.