Triple
T10229885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mineralia |
E243309
|
entity |
| Predicate | basisOfDistinction |
P34582
|
FINISHED |
| Object | presence or absence of life |
—
|
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: presence or absence of life | Statement: [Mineralia, basisOfDistinction, presence or absence of life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisOfDistinction Context triple: [Mineralia, basisOfDistinction, presence or absence of life]
-
A.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
B.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
C.
basisOfClassification
chosen
Indicates that one entity serves as the criterion or foundation used to classify or categorize another entity.
-
D.
prohibitsDiscriminationBasis
Indicates that an entity forbids discriminatory treatment based on specified characteristics or grounds.
-
E.
segregationBasis
Indicates the criterion or characteristic used as the basis for separating or distinguishing one group or set from another.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:19 a.m.