Triple
T25473372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maipure language |
E638364
|
entity |
| Predicate | subfamilyNamesakeOf |
P158577
|
FINISHED |
| Object | Maipurean branch |
—
|
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: Maipurean branch | Statement: [Maipure language, subfamilyNamesakeOf, Maipurean branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subfamilyNamesakeOf Context triple: [Maipure language, subfamilyNamesakeOf, Maipurean branch]
-
A.
subfamilyCommonName
Indicates that a subfamily is associated with a particular commonly used name.
-
B.
subfamily
Indicates that one taxonomic group is a subfamily within a larger family, representing an intermediate rank in biological classification.
-
C.
subfamilyCorrespondence
Indicates a correspondence or mapping between subfamilies, specifying how one subfamily relates or aligns to another within a broader family structure.
-
D.
isLargestSubfamilyOf
Indicates that one group or category is the largest subfamily within another, typically in terms of number of members or size.
-
E.
subfamilyCharacteristic
Indicates that a particular characteristic is shared by, or defines, members of a given subfamily.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7536d78819096ba361d59d01c4f |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:24 p.m.