Triple
T18757625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peridiscaceae |
E458690
|
entity |
| Predicate | hasUnusualMorphology |
P133426
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Peridiscaceae, hasUnusualMorphology, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnusualMorphology Context triple: [Peridiscaceae, hasUnusualMorphology, true]
-
A.
hasMorphologyDistinctFrom
Indicates that the morphology (form or structure) of one entity is different from that of another entity.
-
B.
hasFrequentMorphologicChange
Indicates that an entity regularly undergoes notable changes in its form, structure, or morphology over time or across instances.
-
C.
morphologicalDiversity
Indicates variation in the forms, structures, or shapes of entities within a group or system.
-
D.
hasIrregularShape
Indicates that an entity possesses a form or outline that deviates from a regular, standard, or symmetrical shape.
-
E.
hasDistinctiveShape
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579f359e48190a64b7360dd3bed3a |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:52 a.m.