Triple
T35948639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tetrataenium |
E1039656
|
entity |
| Predicate | familyAssignmentStatus |
P27265
|
FINISHED |
| Object | subject to taxonomic revision |
—
|
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: subject to taxonomic revision | Statement: [Tetrataenium, familyAssignmentStatus, subject to taxonomic revision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyAssignmentStatus Context triple: [Tetrataenium, familyAssignmentStatus, subject to taxonomic revision]
-
A.
previousFamilyAssignment
chosen
Indicates that an entity was formerly assigned to a particular family before a subsequent change or reassignment.
-
B.
currentFamilyStatus
Indicates the present state or condition of an entity’s family situation or relationships.
-
C.
macroFamilyStatus
Indicates the broad genealogical relationship between languages or language families at the macro-family level.
-
D.
familyNameStatus
Indicates the status or condition of a person's family name, such as whether it is current, former, changed, or otherwise designated.
-
E.
familySocialStatus
Indicates the social standing or class position associated with a person’s family within a society.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:07 p.m.