Triple
T17581738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megachilidae |
E428218
|
entity |
| Predicate | containsParasiticTaxa |
P89700
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Megachilidae, containsParasiticTaxa, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsParasiticTaxa Context triple: [Megachilidae, containsParasiticTaxa, true]
-
A.
includesParasiticTaxa
chosen
Indicates that the referenced group or set contains taxa that live parasitically on or within other organisms.
-
B.
includesTaxaWith
Indicates that an entity contains or encompasses one or more specified taxa within its scope or membership.
-
C.
includesScavengingTaxa
Indicates that the referenced group or assemblage contains taxa that engage in scavenging behavior (feeding on dead or decaying organic matter).
-
D.
isParaphyleticInTraditionalSense
Indicates that a group includes some, but not all, descendants of a common ancestor, making it paraphyletic under traditional (often morphology-based) classifications.
-
E.
hasSubtaxon
Indicates that one taxonomic group is a subordinate or included taxon within another taxonomic group.
- 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_69e463ce8eb081909257be47d150aa04 |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.