Triple
T27357215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Mattaponi Indian Tribe |
E685715
|
entity |
| Predicate | recognizedAsTribeByVirginia |
P56771
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [Upper Mattaponi Indian Tribe, recognizedAsTribeByVirginia, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsTribeByVirginia Context triple: [Upper Mattaponi Indian Tribe, recognizedAsTribeByVirginia, 1983]
-
A.
recognizedTribe
Indicates that a group is officially acknowledged as a tribe by a governing or authoritative body.
-
B.
recognizedTribeIncludes
Indicates that a formally recognized tribe encompasses or includes a particular subgroup, member, or entity within its official structure or membership.
-
C.
stateRecognizedTribe
Indicates that a tribe is officially acknowledged and recognized by a state government as a tribal entity.
-
D.
recognizedTribalEntity
Indicates that an entity is officially acknowledged as a tribal nation or community by a governing authority.
-
E.
recognizedAsTribeInYear
chosen
Indicates that an entity was officially recognized or designated as a tribe in a specified year.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 11:52 a.m.