Triple
T15645354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EasyCard |
E376162
|
entity |
| Predicate | hasMaximumStoredValue |
P84602
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [EasyCard, hasMaximumStoredValue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumStoredValue Context triple: [EasyCard, hasMaximumStoredValue, true]
-
A.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
-
B.
hasMaximumBalanceLimit
chosen
Indicates that there is an upper bound on the balance that an account or entity is allowed to hold.
-
C.
isMaximumWhen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
-
D.
hasLimitSet
Indicates that there is a defined boundary, range, or constraint applied to something.
-
E.
hasMaxDraftApprox
Indicates that one entity has, as an upper bound, an approximate maximum value or level for a draft-related quantity associated with another 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed400ec8190a14a9f7cf3092865 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.