Triple
T13859950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockbridge-Munsee Community |
E333164
|
entity |
| Predicate | hasTribalEnrollmentCriteria |
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: [Stockbridge-Munsee Community, hasTribalEnrollmentCriteria, lineal descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalEnrollmentCriteria Context triple: [Stockbridge-Munsee Community, hasTribalEnrollmentCriteria, lineal descent]
-
A.
hasTribalEnrollment
Indicates that an entity is formally enrolled as a member of a specific tribe or tribal nation.
-
B.
tribalEnrollmentBasis
chosen
Indicates the basis or criteria on which an individual’s enrollment or membership in a tribe is determined.
-
C.
linkedToTribalEnrollment
Indicates that one entity has a direct connection or association with another entity’s tribal enrollment status or record.
-
D.
hasTribalPresence
Indicates that a tribal group is present, active, or represented in relation to the referenced entity or location.
-
E.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02de38e48190b6ead95561031c32 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.