Triple
T1526264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo sapiens |
E32342
|
entity |
| Predicate | currentDistribution |
P29815
|
FINISHED |
| Object | worldwide |
—
|
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: worldwide | Statement: [Homo sapiens, currentDistribution, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentDistribution Context triple: [Homo sapiens, currentDistribution, worldwide]
-
A.
previousDistribution
Indicates that one distribution event or state occurred immediately before another in a sequence.
-
B.
currentSystem
Indicates that an entity is the system or configuration that is presently active or in use.
-
C.
hasDistributions
Indicates that an entity is associated with one or more distributions through which it is delivered, provided, or made available.
-
D.
distributedAs
Indicates that something is allocated, delivered, or spread out according to a particular pattern, rule, or distribution scheme.
-
E.
distributionStatus
Indicates the current state or phase of how something is being distributed, such as whether distribution is planned, in progress, completed, or halted.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a933dce3488190b20f0e3d37d16371 |
completed | March 5, 2026, 7:42 a.m. |
Created at: March 4, 2026, 7:26 p.m.