Triple
T289651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principles of Geology |
E5960
|
entity |
| Predicate | opposedTheory |
P3648
|
FINISHED |
| Object | catastrophism |
—
|
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: catastrophism | Statement: [Principles of Geology, opposedTheory, catastrophism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedTheory Context triple: [Principles of Geology, opposedTheory, catastrophism]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
theorized
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
-
C.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
D.
challengedConcept
chosen
Indicates that one entity has questioned, disputed, or called into doubt the validity, accuracy, or applicability of a particular concept.
-
E.
arguesThat
Indicates that one entity presents reasons or justification in support of a specific claim, position, or proposition held about another entity or topic.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e4df5508190ab75115ac6b3964e |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7d089081909810442c3d0182f6 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.