Triple
T5414646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Fuller |
E121099
|
entity |
| Predicate | positionOnKuhn |
P63303
|
FINISHED |
| Object | critical of Kuhn's relativism |
—
|
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: critical of Kuhn's relativism | Statement: [Steve Fuller, positionOnKuhn, critical of Kuhn's relativism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnKuhn Context triple: [Steve Fuller, positionOnKuhn, critical of Kuhn's relativism]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
C.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
D.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
E.
positionInNotation
Indicates the specific place or index that an element occupies within a given ordered notation or representation.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bcace08190932fe85e4b4aeffc |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd865702ec8190831bde2c2a331f28 |
completed | March 20, 2026, 5:39 p.m. |
Created at: March 20, 2026, 2:05 p.m.