Triple
T18757636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peridiscaceae |
E458690
|
entity |
| Predicate | hasScatteredDistribution |
P101893
|
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, hasScatteredDistribution, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScatteredDistribution Context triple: [Peridiscaceae, hasScatteredDistribution, true]
-
A.
hasScatter
Indicates that something is distributed or spread out irregularly or in multiple directions from a central point.
-
B.
hasDistributionType
chosen
Indicates the type or pattern of distribution associated with an entity, specifying how something is spread, allocated, or made available.
-
C.
hasGlobalDistribution
Indicates that the related entity occurs, operates, or is present across most or all regions of the world rather than being confined to a specific locality or region.
-
D.
hasDistributions
Indicates that an entity is associated with one or more distributions through which it is delivered, provided, or made available.
-
E.
distributedAs
Indicates that something is allocated, delivered, or spread out according to a particular pattern, rule, or distribution scheme.
- F. None of above.
Provenance (3 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. |
Created at: April 10, 2026, 11:52 a.m.