Triple
T32687596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Giants |
E835765
|
entity |
| Predicate | commonEnvironmentFeature |
P111300
|
FINISHED |
| Object | snow-capped peaks |
—
|
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: snow-capped peaks | Statement: [Mountain Giants, commonEnvironmentFeature, snow-capped peaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonEnvironmentFeature Context triple: [Mountain Giants, commonEnvironmentFeature, snow-capped peaks]
-
A.
supportsEnvironment
Indicates that one entity provides the necessary conditions, compatibility, or resources for another entity to operate or exist within a particular environment.
-
B.
classicEnvironmentSupport
Indicates that an entity provides compatibility or support for operating in a legacy or traditional computing environment.
-
C.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
D.
configurationFeatures
Indicates the specific options or characteristics that are enabled or defined within a particular configuration.
-
E.
hasGeneralEnvironment
chosen
Indicates that an entity exists or operates within a broad or overall environmental context or setting.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: May 1, 2026, 1:09 a.m.