Triple
T19940280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon Marius |
E479289
|
entity |
| Predicate | opposedModel |
P95906
|
FINISHED |
| Object | Copernican heliocentrism |
—
|
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: Copernican heliocentrism | Statement: [Simon Marius, opposedModel, Copernican heliocentrism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedModel Context triple: [Simon Marius, opposedModel, Copernican heliocentrism]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
theoryOpposed
chosen
Indicates that one theory stands in opposition to, or conflicts with, another theory.
-
C.
opposedApproach
Indicates that one entity actively disagrees with, resists, or works against the method, strategy, or course of action proposed or taken by another entity.
-
D.
opposedProject
Indicates that an entity actively resisted, disagreed with, or worked against a particular project.
-
E.
opposedFocus
Indicates that one entity’s focus, attention, or emphasis is directed in opposition to, or in contrast with, the focus of another entity.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a1a8df4819094e84855465df6c0 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.