Triple
T2915707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware Nation |
E78600
|
entity |
| Predicate | tribalEnrollmentBasis |
P43878
|
FINISHED |
| Object | lineal descent |
—
|
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: lineal descent | Statement: [Delaware Nation, tribalEnrollmentBasis, lineal descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalEnrollmentBasis Context triple: [Delaware Nation, tribalEnrollmentBasis, lineal descent]
-
A.
hasTribalEnrollment
Indicates that an entity is formally enrolled as a member of a specific tribe or tribal nation.
-
B.
federallyRecognizedTribe
Indicates that the subject is officially acknowledged by the federal government as a Native American tribe with a recognized government-to-government relationship.
-
C.
recognizedTribalEntity
Indicates that an entity is officially acknowledged as a tribal nation or community by a governing authority.
-
D.
includedTribalType
Indicates that one entity is classified as belonging to, or being part of, a specified tribal category or type.
-
E.
governingTribalPresence
Indicates that an entity holds governing authority or administrative control over a tribal presence in a given area or context.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:52 p.m.