Triple
T23766498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adversus Noetum |
E587393
|
entity |
| Predicate | opposesTeacher |
P153878
|
FINISHED |
| Object | Noetus of Smyrna |
—
|
NE NERFINISHED |
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: Noetus of Smyrna | Statement: [Adversus Noetum, opposesTeacher, Noetus of Smyrna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposesTeacher Context triple: [Adversus Noetum, opposesTeacher, Noetus of Smyrna]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
theoryOpposed
Indicates that one theory stands in opposition to, or conflicts with, another theory.
-
C.
opposesLabel
Indicates that one entity expresses disagreement with, resistance to, or active opposition against another entity or its position.
-
D.
opposesDivision
Indicates a relationship where one entity actively resists, rejects, or works against the separation or splitting of another entity into parts or groups.
-
E.
opposesPhrase
Indicates that one entity expresses disagreement with, resistance to, or argument against the idea, statement, or position represented by the phrase.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c462ad348190b51bcaf66715a950 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:15 p.m.