Triple
T27316259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nansemond Indian Nation |
E689354
|
entity |
| Predicate | tribalRoll |
P162540
|
FINISHED |
| Object | enrolled citizens |
—
|
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: enrolled citizens | Statement: [Nansemond Indian Nation, tribalRoll, enrolled citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalRoll Context triple: [Nansemond Indian Nation, tribalRoll, enrolled citizens]
-
A.
tribalRank
Indicates the hierarchical status or level an individual holds within a tribe or tribal social structure.
-
B.
tribalCode
Indicates that an entity is governed by, associated with, or identified according to a specific tribal legal or regulatory code.
-
C.
tribalStatus
Indicates that an entity holds a particular affiliation, recognition, or classification with respect to a tribe or tribal community.
-
D.
tribalFunction
Indicates a role, duty, or activity that a tribe or tribal group performs or is responsible for.
-
E.
tribalStandardAssociatedWith
Indicates a relationship where a tribal standard (such as a flag, emblem, or banner) is associated with, represents, or belongs to a particular tribe or tribal group.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f625402d808190be8279d895d2b27f |
completed | May 2, 2026, 4:24 p.m. |
Created at: April 27, 2026, 11:30 a.m.