Triple
T25345407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poilão |
E635532
|
entity |
| Predicate | hasMainTaxonOfInterest |
P73333
|
FINISHED |
| Object | Chelonia mydas |
—
|
NE NERFINISHED |
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: Chelonia mydas | Statement: [Poilão, hasMainTaxonOfInterest, Chelonia mydas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainTaxonOfInterest Context triple: [Poilão, hasMainTaxonOfInterest, Chelonia mydas]
-
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.
hasSubtaxon
Indicates that one taxonomic group is a subordinate or included taxon within another taxonomic group.
-
D.
hasScientificInterestIn
Indicates that one entity holds a scientific curiosity, concern, or research focus directed toward another entity.
-
E.
includesTaxaWith
Indicates that an entity contains or encompasses one or more specified taxa within its scope or membership.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 21, 2026, 1:34 p.m.