Triple
T20142768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ¡Uno! |
E491215
|
entity |
| Predicate | cardNumbersRange |
P138831
|
FINISHED |
| Object | 0–9 |
—
|
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: 0–9 | Statement: [¡Uno!, cardNumbersRange, 0–9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardNumbersRange Context triple: [¡Uno!, cardNumbersRange, 0–9]
-
A.
serialNumberRange
Indicates that there is a specified range of serial numbers within which the related entities or items fall.
-
B.
articleNumberRange
Indicates that something is associated with or falls within a specified range of article numbers.
-
C.
typicalCarNumberRange
Indicates the usual or commonly expected numerical range of cars associated with an entity (such as a location, time period, or context).
-
D.
RVNumberRange
Indicates that a recreational vehicle’s number or identifier falls within a specified numeric range.
-
E.
cardBrandsInvolved
Indicates that specific payment card brands are involved or participate in a given transaction, process, or context.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679bcf2c8190ac6e969178d8acde |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:33 p.m.