Triple
T37461008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y’Shaarj, Rage Unbound |
E930915
|
entity |
| Predicate | effectZoneChange |
P187921
|
FINISHED |
| Object | From deck to battlefield |
—
|
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: From deck to battlefield | Statement: [Y’Shaarj, Rage Unbound, effectZoneChange, From deck to battlefield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectZoneChange Context triple: [Y’Shaarj, Rage Unbound, effectZoneChange, From deck to battlefield]
-
A.
zoneChangeTrigger
chosen
Indicates a condition or event that causes a transition from one defined zone or area to another.
-
B.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
C.
fareZoneChangeBoundary
Indicates a boundary where the applicable fare zone changes from one zone to another.
-
D.
zoneAdded
Indicates that a new zone has been created and incorporated into an existing system, area, or configuration.
-
E.
otherZones
Indicates that an entity is associated with or belongs to zones that are distinct from a primary or reference zone.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 3, 2026, 4:17 p.m.