Triple
T13371591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Intentional Stance |
E319077
|
entity |
| Predicate | stanceType |
P109655
|
FINISHED |
| Object | interpretive stance |
—
|
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: interpretive stance | Statement: [The Intentional Stance, stanceType, interpretive stance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceType Context triple: [The Intentional Stance, stanceType, interpretive stance]
-
A.
personType
Indicates that an entity is classified as a particular type or category of person.
-
B.
typicalConstituentType
Indicates the usual or characteristic type of component that typically makes up or forms part of something.
-
C.
strainType
Indicates the specific variety or subtype classification within a broader category of strains (e.g., biological, chemical, or product strains).
-
D.
allyType
Indicates that one entity is classified as a specific type or category of ally in relation to another entity.
-
E.
designationType
Indicates the specific category or kind of formal status, title, or label that has been assigned in a designation relationship.
- F. None of above. chosen
Provenance (4 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd8950481909785a2060f43b6ed |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:33 p.m.