Triple
T473457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fabaceae |
E9008
|
entity |
| Predicate | rankAmongLargestPlantFamilies |
P13437
|
FINISHED |
| Object | one of the three largest angiosperm families |
—
|
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: one of the three largest angiosperm families | Statement: [Fabaceae, rankAmongLargestPlantFamilies, one of the three largest angiosperm families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankAmongLargestPlantFamilies Context triple: [Fabaceae, rankAmongLargestPlantFamilies, one of the three largest angiosperm families]
-
A.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
B.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
C.
numberOfGenera
Indicates the total count of genera associated with or contained within a given entity.
-
D.
plantHeight
Indicates the measured vertical size or growth extent of a plant from its base to its top.
-
E.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0208c788190a96cdabcf593fda7 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeba8a488190986cc7381332f783 |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.