Triple
T18245290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Maktoum Challenge Round 2 |
E436933
|
entity |
| Predicate | typicalPurseRangeUSD |
P131010
|
FINISHED |
| Object | 200000–250000 |
—
|
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: 200000–250000 | Statement: [Al Maktoum Challenge Round 2, typicalPurseRangeUSD, 200000–250000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPurseRangeUSD Context triple: [Al Maktoum Challenge Round 2, typicalPurseRangeUSD, 200000–250000]
-
A.
approximatePurse
Indicates that one entity estimates or comes close to determining the value, amount, or contents of another entity’s purse or collection of resources.
-
B.
purse
Indicates attempting to influence or persuade someone to adopt a particular course of action, belief, or decision.
-
C.
currencyOfPurse
Indicates the type of currency that is contained in or associated with a given purse.
-
D.
redPurseTraditionallyContains
Indicates that, by custom or tradition, a red purse is expected to hold or contain a particular item or set of items.
-
E.
currencyOfPurseScale
Indicates the type or unit of currency used to measure or express the value or contents of a purse at a given scale.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e6fbac8190bf252c4337f50c29 |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:33 a.m.