Triple
T37464497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twinspell |
E930999
|
entity |
| Predicate | copyCreatedCanBeBurnedIfHandIsFull |
P189762
|
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: [Twinspell, copyCreatedCanBeBurnedIfHandIsFull, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: copyCreatedCanBeBurnedIfHandIsFull Context triple: [Twinspell, copyCreatedCanBeBurnedIfHandIsFull, true]
-
A.
hasBurnUnit
Indicates that one entity (typically a medical facility) includes or is equipped with a specialized unit dedicated to the treatment and care of burn patients.
-
B.
hasHand
Indicates that an entity possesses or is equipped with a hand (or hands) as part of its body or structure.
-
C.
flameHandedOverAt
Indicates that a symbolic flame or torch is formally transferred from one holder or location to another at a specific time or event.
-
D.
hasNumberOfHands
Indicates the specific count of hands that an entity possesses.
-
E.
bestHandCardsUsed
Indicates that the specified cards are the ones actually used to form the player's best possible hand in a given game situation.
- 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_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: May 3, 2026, 4:17 p.m.