Triple
T37461936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Kraken |
E930938
|
entity |
| Predicate | hasBalanceChangesFor |
P195377
|
FINISHED |
| Object | Classic cards |
—
|
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: Classic cards | Statement: [Year of the Kraken, hasBalanceChangesFor, Classic cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBalanceChangesFor Context triple: [Year of the Kraken, hasBalanceChangesFor, Classic cards]
-
A.
balancesWith
Indicates that two entities are in a state of equilibrium or mutual offset, such that each counterbalances or matches the other in a specified context.
-
B.
historicalBalance
Indicates a relationship where an entity’s past or previous balance amount is recorded or referenced over time.
-
C.
hasOnlineBalanceCheck
Indicates that an entity provides the capability to check a balance via an online interface or service.
-
D.
hasRebalancing
Indicates that an entity undergoes or is subject to an adjustment process to restore a desired balance or allocation among its components or related elements.
-
E.
bondChange
Indicates a change in the type, order, or presence of a bond between two entities, such as forming, breaking, or altering a connection.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: May 3, 2026, 4:17 p.m.