Triple
T3494810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California linguistic area |
E73824
|
entity |
| Predicate | hasReferenceWork |
P48731
|
FINISHED |
| Object | studies of California Indian languages |
—
|
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: studies of California Indian languages | Statement: [California linguistic area, hasReferenceWork, studies of California Indian languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferenceWork Context triple: [California linguistic area, hasReferenceWork, studies of California Indian languages]
-
A.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
-
B.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion to, another entity.
-
C.
hasWorkUsedBy
Indicates that a work (such as a resource, document, or artifact) is utilized or referenced by another entity in performing its activities or functions.
-
D.
hasWorkInCollection
Indicates that a work or item is included as part of a particular collection.
-
E.
hasWorkAsSubject
Indicates that an entity serves as the subject (creator or originator) of a particular work or creative output.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbaebed881909d9cbc9c4c1f138f |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb055ed2481908171effe28151cf9 |
completed | March 8, 2026, 5:22 p.m. |
Created at: March 8, 2026, 3:18 p.m.