Triple
T13166448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evian |
E312860
|
entity |
| Predicate | sourceEnvironment |
P853
|
FINISHED |
| Object | Alpine springs |
—
|
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: Alpine springs | Statement: [Evian, sourceEnvironment, Alpine springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceEnvironment Context triple: [Evian, sourceEnvironment, Alpine springs]
-
A.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
B.
carbonSource
Indicates that one entity serves as the source or provider of carbon for another entity or process.
-
C.
environmentType
chosen
Indicates the kind or category of environment associated with an entity or situation.
-
D.
supportsEnvironment
Indicates that one entity provides the necessary conditions, compatibility, or resources for another entity to operate or exist within a particular environment.
-
E.
sourceCategory
Indicates the classification or type from which something originates or is derived.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:13 p.m.