Triple
T12036705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vahliales |
E286558
|
entity |
| Predicate | isMonofamilial |
P102879
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Vahliales, isMonofamilial, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMonofamilial Context triple: [Vahliales, isMonofamilial, true]
-
A.
isMonogenetic
Indicates that something originates from or is derived from a single source, cause, or ancestral line.
-
B.
hasFamilialForm
Indicates that one entity has a version, variant, or form that is specifically used in familial or family-related contexts in relation to another entity.
-
C.
monogeneric
Indicates that a taxonomic group (such as a family or subfamily) contains only a single genus.
-
D.
hasCentralFamily
Indicates that an entity possesses or is organized around a primary or core family unit.
-
E.
recognizedAsSeparateFamily
Indicates that one entity is formally acknowledged or classified as belonging to a distinct, separate family from another entity.
- F. None of above. chosen
Provenance (4 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:47 p.m.