Triple
T748188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Henry Huxley |
E15388
|
entity |
| Predicate | supportedTheory |
P9427
|
FINISHED |
| Object | evolution by natural selection |
—
|
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: evolution by natural selection | Statement: [Thomas Henry Huxley, supportedTheory, evolution by natural selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedTheory Context triple: [Thomas Henry Huxley, supportedTheory, evolution by natural selection]
-
A.
supportsTheory
chosen
Indicates that one entity provides evidence, justification, or endorsement for the validity or acceptance of another entity’s theory.
-
B.
appliesTheory
Indicates that an entity uses or implements a particular theory in analyzing, explaining, or addressing something.
-
C.
supportsPrinciple
Indicates that one entity endorses, upholds, or actively backs a particular principle or doctrine.
-
D.
supportedResearch
Indicates that one entity provided assistance, resources, or backing to enable or advance the research activities of another entity.
-
E.
theorized
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a62f31888190b80cb0a7220f8d80 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.