Triple
T21844135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yima |
E539330
|
entity |
| Predicate | purposeOfVara |
P145534
|
FINISHED |
| Object | preserve life from deadly winter |
—
|
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: preserve life from deadly winter | Statement: [Yima, purposeOfVara, preserve life from deadly winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfVara Context triple: [Yima, purposeOfVara, preserve life from deadly winter]
-
A.
usesVAR
Indicates that one entity makes use of, employs, or utilizes another entity as a variable or resource in performing some function or operation.
-
B.
purposeOfConstruction
Indicates that one entity was constructed or built in order to serve, enable, or fulfill the function, goal, or intended use represented by another entity.
-
C.
purposeOfRegime
Indicates the goal, function, or intended role that a particular regime is designed or established to fulfill.
-
D.
damPurpose
Indicates the primary function or intended use for which a dam has been constructed or is operated.
-
E.
purposeOfLaw
Indicates that a law exists or is designed for a particular goal, function, or intended effect.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd5248f08190ba208512eafbe7ad |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c187bc548190b4ca13150f6bae38 |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 6:55 p.m.