Triple
T4637891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelicerata |
E101578
|
entity |
| Predicate | includesOrganismGroup |
P10571
|
FINISHED |
| Object | spiders |
—
|
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: spiders | Statement: [Chelicerata, includesOrganismGroup, spiders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesOrganismGroup Context triple: [Chelicerata, includesOrganismGroup, spiders]
-
A.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
B.
includesSpeciesFrom
Indicates that one collection, group, or set contains one or more species that originate from or belong to another specified source or context.
-
C.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
D.
supportsSpeciesGroup
Indicates that one entity provides suitable conditions or resources that enable the survival or persistence of a particular group of species.
-
E.
containsGroup
chosen
Indicates that one entity includes or encompasses a specific group of entities within 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a64214481908a207e8070cc7a45 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.