Triple
T25142305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Muy |
E629833
|
entity |
| Predicate | hasMainTaxonomicGroupOfInterest |
P73333
|
FINISHED |
| Object | birds |
—
|
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: birds | Statement: [De Muy, hasMainTaxonomicGroupOfInterest, birds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainTaxonomicGroupOfInterest Context triple: [De Muy, hasMainTaxonomicGroupOfInterest, birds]
-
A.
hasMainTaxonomicFocus
chosen
Indicates that something (such as a work, study, or resource) primarily concerns or centers on a particular taxon as its main subject of taxonomic focus.
-
B.
hasImportantTaxonGroup
Indicates that an entity is associated with a taxonomic group considered particularly significant or relevant in a given biological or classification context.
-
C.
hasScientificInterestIn
Indicates that one entity holds a scientific curiosity, concern, or research focus directed toward another entity.
-
D.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
E.
hasScientificSpecies
Indicates that an entity is associated with a specific scientific (Latin) species name.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 18, 2026, 6:29 a.m.