Triple
T27342260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kota Petir |
E684137
|
entity |
| Predicate | characteristicHighlighted |
P89469
|
FINISHED |
| Object | frequent thunderstorms |
—
|
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: frequent thunderstorms | Statement: [Kota Petir, characteristicHighlighted, frequent thunderstorms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicHighlighted Context triple: [Kota Petir, characteristicHighlighted, frequent thunderstorms]
-
A.
highlightsAttributeOf
chosen
Indicates that one entity draws attention to, emphasizes, or showcases a particular attribute or property of another entity.
-
B.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
C.
valueCharacteristic
Indicates that one entity serves as a value or specific quantitative/qualitative measure that characterizes or describes another entity.
-
D.
notableCollectionCharacteristic
Indicates that a collection is distinguished by a particular defining feature or quality that makes it notable.
-
E.
primaryCharacteristics
Indicates the main defining traits or features that most fundamentally characterize an entity.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 11:43 a.m.