Triple
T26888771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | zebra |
E677113
|
entity |
| Predicate | antiParasiteHypothesis |
P125532
|
FINISHED |
| Object | stripes may deter biting flies |
—
|
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: stripes may deter biting flies | Statement: [zebra, antiParasiteHypothesis, stripes may deter biting flies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antiParasiteHypothesis Context triple: [zebra, antiParasiteHypothesis, stripes may deter biting flies]
-
A.
parasitizes
Indicates a relationship in which one organism lives on or in another organism, deriving nutrients or benefits at the host’s expense.
-
B.
hypothesis
chosen
Indicates that a statement or proposition is tentatively assumed to be true and is subject to testing, evaluation, or proof.
-
C.
toxinSourceHypothesis
Indicates a hypothesized or proposed source from which a toxin originates or is derived.
-
D.
contradictedTheory
Indicates that one entity has presented evidence, arguments, or findings that oppose, challenge, or invalidate the theory proposed by another entity.
-
E.
pestOf
Indicates that one entity acts as a pest to another, typically causing harm, damage, or nuisance to it.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61f66aeac819080748c6a0fb95f9b |
completed | May 2, 2026, 3:59 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:43 a.m.