Triple
T7206151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarsipedidae |
E148670
|
entity |
| Predicate | monotypicStatus |
P19345
|
FINISHED |
| Object | monotypic or nearly monotypic family |
—
|
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: monotypic or nearly monotypic family | Statement: [Tarsipedidae, monotypicStatus, monotypic or nearly monotypic family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monotypicStatus Context triple: [Tarsipedidae, monotypicStatus, monotypic or nearly monotypic family]
-
A.
singleType
Indicates that an entity belongs to exactly one specific type or category, with no additional types assigned.
-
B.
monogeneric
chosen
Indicates that a taxonomic group (such as a family or subfamily) contains only a single genus.
-
C.
isMonogenetic
Indicates that something originates from or is derived from a single source, cause, or ancestral line.
-
D.
hasUniqueStatus
Indicates that an entity possesses a status or condition that is distinct and not shared with any other entity in the given context.
-
E.
isMonotherapy
Indicates that a treatment is used alone, without being combined with any other therapies.
- 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_69c687e8cf188190b5f3ecffd681f04e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e94ef5cc81908c33adcedf5c5054 |
completed | March 27, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.