Triple
T6317784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salinan people |
E141656
|
entity |
| Predicate | hasModernDescendants |
P36141
|
FINISHED |
| Object | Salinan descendants in California |
—
|
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: Salinan descendants in California | Statement: [Salinan people, hasModernDescendants, Salinan descendants in California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernDescendants Context triple: [Salinan people, hasModernDescendants, Salinan descendants in California]
-
A.
hasModernSuccessor
Indicates that an entity is followed or replaced by another entity that serves as its modern equivalent or continuation.
-
B.
hasModernNamesake
Indicates that an entity is the namesake or inspiration for a modern entity that shares or derives its name from it.
-
C.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
D.
modernLanguageDescendant
Indicates that one language is a direct or indirect descendant of another language in the modern era.
-
E.
hasDescendantPeople
chosen
Indicates that one entity has other people as its descendants in a genealogical or lineage-based relationship.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c25530819080b29e0029175c00 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.