Triple
T38356836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aphloiaceae |
E1046354
|
entity |
| Predicate | APGIIClassification |
P190459
|
FINISHED |
| Object | recognized |
—
|
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: recognized | Statement: [Aphloiaceae, APGIIClassification, recognized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: APGIIClassification Context triple: [Aphloiaceae, APGIIClassification, recognized]
-
A.
classificationReference
Indicates that one entity serves as a reference or source for the classification or categorization applied to another entity.
-
B.
WHOClassification
Indicates that an entity is categorized according to the World Health Organization’s official classification system.
-
C.
UICClassification
Indicates the standardized classification or coding assigned to an entity according to the UIC (International Union of Railways) system.
-
D.
governingClassification
Indicates the classification system or category framework that determines how an entity is organized, labeled, or regulated.
-
E.
classificationOf
Indicates that one entity serves as a classification, category, or type under which another entity is grouped or organized.
- 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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fcc7a42f68819081d6ec8bb6b53438 |
completed | May 7, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:31 p.m.