Triple
T31916682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford Encyclopedia of Philosophy |
E814849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reference work in philosophy |
C13828
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: reference work in philosophy Context triple: [Stanford Encyclopedia of Philosophy, instanceOf, reference work in philosophy]
-
A.
online reference work
chosen
An online reference work is a digitally accessible, systematically organized collection of authoritative information designed for quick consultation and research.
-
B.
work of continental philosophy
A work of continental philosophy is a text that engages critically and often historically with questions of meaning, subjectivity, power, and culture, typically using interpretive, phenomenological, or dialectical methods rather than formal analytic argumentation.
-
C.
philosophy book
A philosophy book is a written work that systematically explores fundamental questions about existence, knowledge, values, reason, mind, and language, often presenting arguments and theories from one or more philosophical perspectives.
-
D.
philosophical corpus
A philosophical corpus is a structured collection of philosophical texts, arguments, and commentaries that together represent the intellectual output of one or more thinkers, traditions, or periods.
-
E.
historical reference work
A historical reference work is a systematically organized resource that compiles verified information, dates, events, and interpretations about the past for quick consultation and scholarly use.
- F. None of above.
Provenance (1 batch)
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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:02 a.m.