Triple
T17596284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organon |
E428579
|
entity |
| Predicate | inAristotleCorpus |
P86363
|
FINISHED |
| Object | logical works |
—
|
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: logical works | Statement: [Organon, inAristotleCorpus, logical works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inAristotleCorpus Context triple: [Organon, inAristotleCorpus, logical works]
-
A.
workInPlatoCorpus
Indicates that an entity is a work that appears within the corpus of texts attributed to Plato.
-
B.
workOfPhilosopher
Indicates that the subject is a philosophical work created or authored by the philosopher represented by the object.
-
C.
consideredByAristotleAs
chosen
Indicates that something is regarded or classified in a particular way according to Aristotle’s views or writings.
-
D.
philosophicalWork
Indicates that one entity is a philosophical work (such as a text, treatise, or piece of writing) created, authored, or associated with another entity.
-
E.
producedPhilosopher
Indicates that one entity (such as a place, institution, or context) brought about, gave rise to, or was responsible for the development of a particular philosopher.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469ec335c8190abcaff700cfff23b |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.