Triple
T35988632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cephalotaceae |
E1040780
|
entity |
| Predicate | describedAsFamilyBy |
P194439
|
FINISHED |
| Object | Robert Brown |
—
|
NE NERFINISHED |
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: Robert Brown | Statement: [Cephalotaceae, describedAsFamilyBy, Robert Brown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedAsFamilyBy Context triple: [Cephalotaceae, describedAsFamilyBy, Robert Brown]
-
A.
describedAsFamilyIn
Indicates that one entity is characterized or referred to as family in the context of another entity or setting.
-
B.
describedInFamily
Indicates that an entity is mentioned or characterized within a specific family-related context, such as a family record, lineage, or family description.
-
C.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
identifiedAsFamilyIn
Indicates that one entity is recognized or designated as a family member within the context of a specified group, record, or setting.
-
E.
familyDescription
Indicates a descriptive statement that characterizes or summarizes the nature, structure, or dynamics of a family relationship.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: May 3, 2026, 4:07 p.m.