Triple
T21752609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pure Life |
E536950
|
entity |
| Predicate | isWidelyDistributed |
P32890
|
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: [Pure Life, isWidelyDistributed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWidelyDistributed Context triple: [Pure Life, isWidelyDistributed, true]
-
A.
geographicDistribution
Indicates the spatial range or area over which something occurs, exists, or is found.
-
B.
hasGlobalDistribution
chosen
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.
-
C.
hasWildPopulationOf
Indicates that a location or area contains a naturally occurring, non-captive population of the specified species.
-
D.
geographicRangeType
Indicates the kind of geographic range or distribution pattern that characterizes where an entity occurs or is found.
-
E.
isMoreGeographicallyDispersedThan
Indicates that one entity’s locations or presence are spread out over a wider or more scattered geographic area than another entity’s.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8b8b9c8190b1f6a8bc25d69dbb |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.