Triple
T37568344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | edoi1259 |
E934621
|
entity |
| Predicate | usedInSubfield |
P131163
|
FINISHED |
| Object | historical linguistics |
—
|
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: historical linguistics | Statement: [edoi1259, usedInSubfield, historical linguistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInSubfield Context triple: [edoi1259, usedInSubfield, historical linguistics]
-
A.
containsAsSubfield
Indicates that one field or data structure includes another field as a nested or component subfield within it.
-
B.
belongsToSubfield
chosen
Indicates that one field, topic, or area of study is a more specialized part within a broader academic or disciplinary field.
-
C.
usedInStructure
Indicates that something (such as a material, component, or element) is employed as part of the composition or construction of a larger structure.
-
D.
usedInRecord
Indicates that something (e.g., a resource, value, or element) is utilized or referenced within a particular record.
-
E.
usedInFormat
Indicates that something (such as a method, standard, or component) is employed or applied within a particular format.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:17 p.m.