Triple
T5185596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Organon |
E117022
|
entity |
| Predicate | methodEmphasizes |
P17414
|
FINISHED |
| Object | systematic experimentation |
—
|
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: systematic experimentation | Statement: [New Organon, methodEmphasizes, systematic experimentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodEmphasizes Context triple: [New Organon, methodEmphasizes, systematic experimentation]
-
A.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
B.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
C.
nicknameEmphasizes
Indicates that a nickname highlights or draws special attention to a particular characteristic, trait, or aspect of the entity it refers to.
-
D.
marketingNameEmphasizes
Indicates that a marketing name highlights or draws special attention to a particular feature, attribute, or aspect of something.
-
E.
emphasizesAttributeOfHermes
Indicates that something highlights or draws special attention to a particular attribute or characteristic of Hermes.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c269148190badbaf9832a194c0 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.