Triple
T37458962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antique Healbot |
E930869
|
entity |
| Predicate | deckRole |
P100032
|
FINISHED |
| Object | control decks |
—
|
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: control decks | Statement: [Antique Healbot, deckRole, control decks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deckRole Context triple: [Antique Healbot, deckRole, control decks]
-
A.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
B.
roleInGameplay
chosen
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
C.
themeRole
Indicates that an entity is the primary participant undergoing or affected by the action or event expressed by a predicate.
-
D.
tourRole
Indicates the specific function, capacity, or responsibility an entity has within the context of a tour.
-
E.
theaterRole
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
- 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_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.