Triple
T2233605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabo language |
E49226
|
entity |
| Predicate | researchPriority |
P37238
|
FINISHED |
| Object | high for language documentation |
—
|
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: high for language documentation | Statement: [Shabo language, researchPriority, high for language documentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchPriority Context triple: [Shabo language, researchPriority, high for language documentation]
-
A.
researchTopic
Indicates that a subject conducts or focuses research on a particular topic or area of study.
-
B.
researchContext
Indicates the situational, methodological, or thematic setting within which a particular piece of research is conducted or interpreted.
-
C.
researchStrength
Indicates the degree to which an entity possesses strong capabilities, performance, or impact in conducting research.
-
D.
researchCenter
Indicates that one entity functions as a research center associated with, operated by, or focused on the other entity.
-
E.
researchProgram
Indicates that an entity is engaged in, associated with, or part of a structured research initiative or program.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0913f1c8190ac9cfeb0f1c84a76 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf9c77fc8190a323bcaf644fb2c5 |
completed | March 7, 2026, 6:03 a.m. |
Created at: March 4, 2026, 7:47 p.m.