Triple
T1328547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trema |
E28386
|
entity |
| Predicate | previousFamilyAssignment |
P27265
|
FINISHED |
| Object | Ulmaceae |
—
|
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: Ulmaceae | Statement: [Trema, previousFamilyAssignment, Ulmaceae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousFamilyAssignment Context triple: [Trema, previousFamilyAssignment, Ulmaceae]
-
A.
parentFormation
Indicates that one geological formation serves as the larger or originating unit from which another formation is derived or classified.
-
B.
fosterParents
Indicates a relationship where individuals act as temporary parental caregivers for a child who is not their biological or adopted offspring.
-
C.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
D.
neighboringFamily
Indicates that one family lives next to or very close to another family, forming a direct neighborhood relationship.
-
E.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c1d8188190b15a641a08345adc |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0b1326081909aa6beec0cfe8d6c |
completed | March 1, 2026, 10:41 p.m. |
Created at: March 1, 2026, 7:55 p.m.