Triple
T692896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principia Ethica |
E13832
|
entity |
| Predicate | hasPhilosophicalStance |
P4931
|
FINISHED |
| Object | moral realism |
—
|
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: moral realism | Statement: [Principia Ethica, hasPhilosophicalStance, moral realism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhilosophicalStance Context triple: [Principia Ethica, hasPhilosophicalStance, moral realism]
-
A.
philosophicalPositionExpressed
chosen
Indicates that an entity articulates, endorses, or otherwise conveys a specific philosophical stance, view, or doctrine.
-
B.
philosophicalTheme
Indicates that a work, idea, or discourse centrally involves or explores a particular philosophical concept, question, or line of thought.
-
C.
philosophicalConcept
Indicates that one entity is a philosophical concept that characterizes, explains, or is thematically central to the other entity.
-
D.
philosophicalMethod
Indicates the method, approach, or technique used in conducting philosophical inquiry or reasoning.
-
E.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0b05f2c8190876c73db15b489a2 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.