Triple
T12961808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alzateaceae |
E321162
|
entity |
| Predicate | describedAsFamilyIn |
P107716
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Alzateaceae, describedAsFamilyIn, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedAsFamilyIn Context triple: [Alzateaceae, describedAsFamilyIn, 20th century]
-
A.
describedInFamily
Indicates that an entity is mentioned or characterized within a specific family-related context, such as a family record, lineage, or family description.
-
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.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
familyDescription
Indicates a descriptive statement that characterizes or summarizes the nature, structure, or dynamics of a family relationship.
-
E.
representsFamily
Indicates that one entity is related to another through a familial relationship (by blood, marriage, or adoption).
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e5811f481908178fac6d2e0efcd |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:17 p.m.