Triple

T33534961
Position Surface form Disambiguated ID Type / Status
Subject Mamanatowick E858894 entity
Predicate confederacyType P25749 FINISHED
Object loose alliance of semi-autonomous 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: loose alliance of semi-autonomous tribes | Statement: [Mamanatowick, confederacyType, loose alliance of semi-autonomous tribes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: confederacyType
Context triple: [Mamanatowick, confederacyType, loose alliance of semi-autonomous tribes]
  • A. confederateForcesType
    Indicates the type or classification of confederate forces involved in a given military or conflict-related context.
  • B. confederationType chosen
    Indicates the specific kind or category of confederative relationship that exists between the associated entities.
  • C. joinedConfederateStatesOfAmerica
    Indicates that an entity became a member of, or formally aligned itself with, the Confederate States of America.
  • D. formerConfederation
    Indicates that an entity was previously part of a confederation but is no longer a member.
  • E. confederation1
    Indicates a relationship where multiple entities join together in a loose alliance or union while retaining their individual autonomy.
  • 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_69f34978caf4819083f90eba4944d8e8 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fb2e940d5c8190bceae77daf4ef512 completed May 6, 2026, 12:05 p.m.
PD Predicate disambiguation batch_69f9fec70bd881909c658a3c5020318b completed May 5, 2026, 2:29 p.m.
Created at: May 1, 2026, 1:39 a.m.