Triple
T27881534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSSAH |
E705102
|
entity |
| Predicate | integratesDisciplineType |
P166386
|
FINISHED |
| Object | social inquiry |
—
|
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: social inquiry | Statement: [CSSAH, integratesDisciplineType, social inquiry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratesDisciplineType Context triple: [CSSAH, integratesDisciplineType, social inquiry]
-
A.
disciplineCombination
chosen
Indicates a relationship where multiple disciplines are combined or integrated into a unified or joint context.
-
B.
associatedWithDiscipline
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
-
C.
typeDiscipline
Indicates that an entity is associated with, categorized under, or characterized by a particular discipline or field of study.
-
D.
disciplineCode
Indicates the specific field, subject area, or branch of study/classification to which an entity is assigned or categorized.
-
E.
governingDiscipline
Indicates that one discipline or field provides the primary rules, principles, or framework that regulate or guide another activity, domain, or practice.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 6:30 p.m.