Triple
T2653070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | analytic philosophy |
E53945
|
entity |
| Predicate | hasCoreMethod |
P9095
|
FINISHED |
| Object | logical analysis |
—
|
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: logical analysis | Statement: [analytic philosophy, hasCoreMethod, logical analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreMethod Context triple: [analytic philosophy, hasCoreMethod, logical analysis]
-
A.
hasCoreClass
Indicates that an entity is associated with, or belongs to, a primary or fundamental class within a classification system.
-
B.
hasCoreBehavior
Indicates that an entity possesses or exhibits a fundamental, defining behavior that is central to its function or identity.
-
C.
hasWorkingMethod
chosen
Indicates that one entity possesses or employs a functional method, procedure, or technique to achieve a particular task or outcome.
-
D.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
E.
hasCoreState
Indicates that an entity possesses or is associated with a fundamental or primary state that defines its core condition or behavior.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abda0ba2208190ad87763ecbef8c3c |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd815d06481909535c02b0aba8553 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.