Triple
T27882140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shodhania |
E705117
|
entity |
| Predicate | includedInFamilyWithCommonName |
P61588
|
FINISHED |
| Object | fairywrens |
—
|
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: fairywrens | Statement: [Shodhania, includedInFamilyWithCommonName, fairywrens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInFamilyWithCommonName Context triple: [Shodhania, includedInFamilyWithCommonName, fairywrens]
-
A.
belongsToFamilyCommonName
chosen
Indicates that an entity is associated with, or classified under, a particular family-level common name.
-
B.
identifiedAsFamilyIn
Indicates that one entity is recognized or designated as a family member within the context of a specified group, record, or setting.
-
C.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
D.
includesSpeciesCommonName
Indicates that an entity contains or specifies the common (vernacular) name of a species.
-
E.
familyIncludesGenus
Indicates that a family taxonomic rank contains or encompasses a particular genus within its classification.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: April 27, 2026, 6:30 p.m.