Triple
T27320194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chickahominy Indian Tribe |
E689468
|
entity |
| Predicate | hasPeoplehood |
P65880
|
FINISHED |
| Object | Chickahominy Nation |
—
|
NE NERFINISHED |
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: Chickahominy Nation | Statement: [Chickahominy Indian Tribe, hasPeoplehood, Chickahominy Nation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeoplehood Context triple: [Chickahominy Indian Tribe, hasPeoplehood, Chickahominy Nation]
-
A.
peoplehood
chosen
Indicates a relationship in which individuals share a common collective identity, culture, or heritage that binds them together as a distinct people.
-
B.
includesPeopleOf
Indicates that a group, organization, or entity contains or encompasses certain people as its members or participants.
-
C.
hasNonHumanResident
Indicates that a place or location is inhabited or occupied by one or more non-human entities.
-
D.
hasPeopleName
Indicates that an entity is associated with a specific person's name.
-
E.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 11:32 a.m.