Triple
T12920720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köppen BWk |
E309110
|
entity |
| Predicate | hasFirstLetterMeaning |
P27718
|
FINISHED |
| Object | B = arid 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: B = arid climate | Statement: [Köppen BWk, hasFirstLetterMeaning, B = arid climate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstLetterMeaning Context triple: [Köppen BWk, hasFirstLetterMeaning, B = arid climate]
-
A.
hasLastThreeLettersMeaning
Indicates that the last three letters of one entity (typically a word or string) together form a meaningful unit or have a specific semantic significance.
-
B.
hasInitialLetters
Indicates that one entity’s initial letters or acronym are derived from or correspond to the other entity.
-
C.
firstLetter
Indicates that one entity is the initial character or starting letter of another entity (typically a string or word).
-
D.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
E.
hasPrefixMeaning
chosen
Indicates that one entity serves as a semantic prefix of another, contributing a specific meaning to the start of the second 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e7f6e881908c7bb12283898c80 |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.