Triple
T34012380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mundu |
E872148
|
entity |
| Predicate | isWornInClimate |
P56311
|
FINISHED |
| Object | tropical |
—
|
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: tropical | Statement: [Mundu, isWornInClimate, tropical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWornInClimate Context triple: [Mundu, isWornInClimate, tropical]
-
A.
designedForClimate
chosen
Indicates that something has been intentionally created or adapted to function optimally under specific climate or environmental conditions.
-
B.
mayBeWorn
Indicates that one entity is suitable or allowed to be worn by another entity, typically as clothing, accessories, or adornment.
-
C.
alsoWornIn
Indicates that an item of clothing or accessory is additionally worn in another context, location, or time beyond the primary one mentioned.
-
D.
requiresEquipmentInWinter
Indicates that performing the related activity or fulfilling the related condition necessitates the use of specific equipment during winter.
-
E.
wornAt
Indicates that an item is being worn on a specific part of the body or at a particular time or event.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.