Triple
T26529145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | longyi |
E670770
|
entity |
| Predicate | practicalFor |
P98
|
FINISHED |
| Object | hot climate |
—
|
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: hot climate | Statement: [longyi, practicalFor, hot climate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: practicalFor Context triple: [longyi, practicalFor, hot climate]
-
A.
actualPractice
Indicates that an action, method, or behavior is carried out in reality or in day-to-day use, as opposed to being merely theoretical, planned, or prescribed.
-
B.
featuresPracticalEffects
Indicates that something includes or makes use of practical (physical, non-digital) effects as part of its realization or presentation.
-
C.
publicPractice
Indicates that an activity, behavior, or belief is carried out openly in public or within a community setting rather than privately.
-
D.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
isPerfectFor
Indicates that one entity is ideally suited or optimally appropriate for another entity, purpose, or context.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f5ec28819099ec679f636d61d9 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:34 a.m.