Triple
T26738124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tityridae |
E674171
|
entity |
| Predicate | reclassificationBasis |
P34582
|
FINISHED |
| Object | molecular phylogenetic studies |
—
|
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: molecular phylogenetic studies | Statement: [Tityridae, reclassificationBasis, molecular phylogenetic studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reclassificationBasis Context triple: [Tityridae, reclassificationBasis, molecular phylogenetic studies]
-
A.
reclassifiedBy
Indicates that an entity’s classification or category has been changed by a specific agent or authority.
-
B.
reclassifiedAs
Indicates that an entity’s classification or category has been changed from a previous one to a new one.
-
C.
reclassificationYear
Indicates the year in which something was reassigned to a different category, status, or classification.
-
D.
recognitionBasis
Indicates the grounds, criteria, or evidence upon which something or someone is acknowledged, identified, or formally recognized.
-
E.
basisOfClassification
chosen
Indicates that one entity serves as the criterion or foundation used to classify or categorize another entity.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61845e4e8819089d73f9cba43c8b0 |
completed | May 2, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:48 a.m.