Triple
T3539124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salinan language |
E74838
|
entity |
| Predicate | lossCause |
P694
|
FINISHED |
| Object | language shift to Spanish |
—
|
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: language shift to Spanish | Statement: [Salinan language, lossCause, language shift to Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lossCause Context triple: [Salinan language, lossCause, language shift to Spanish]
-
A.
lossType
Indicates the specific category or nature of a loss associated with an entity or event.
-
B.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
C.
loserStatus
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
-
D.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
lost
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbcca5e008190abcfe40c8902a95f |
completed | March 8, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.