Triple
T31588087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Histoire naturelle des rainettes, des grenouilles et des crapauds (1799) |
E806009
|
entity |
| Predicate | taxonomicGroupCovered |
P16820
|
FINISHED |
| Object | Anura |
—
|
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: Anura | Statement: [Histoire naturelle des rainettes, des grenouilles et des crapauds (1799), taxonomicGroupCovered, Anura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonomicGroupCovered Context triple: [Histoire naturelle des rainettes, des grenouilles et des crapauds (1799), taxonomicGroupCovered, Anura]
-
A.
taxonGroup
chosen
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
B.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
C.
taxonType
Indicates the biological or taxonomic rank/category that characterizes a given taxon.
-
D.
namedTaxon
Indicates that an entity is identified as, or associated with, a particular taxonomic name.
-
E.
taxonomicDomain
Indicates that one entity is the biological taxonomic domain to which the other entity belongs.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 30, 2026, 10:26 p.m.