Triple
T36960517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaingun |
E914294
|
entity |
| Predicate | playerCanAcquire |
P188361
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Chaingun, playerCanAcquire, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerCanAcquire Context triple: [Chaingun, playerCanAcquire, Yes]
-
A.
canGain
chosen
Indicates that one entity has the potential or ability to obtain, acquire, or increase something from another entity or source.
-
B.
canTradeWithPlayer
Indicates that an entity is allowed to engage in trading interactions or exchanges with a player.
-
C.
canBeEarnedBy
Indicates that something (such as a reward, status, or resource) is obtainable through the actions, efforts, or qualifications of a particular entity.
-
D.
canEarnOn
Indicates that an entity is able or permitted to receive or generate earnings from another entity, source, or activity.
-
E.
canBorrowFrom
Indicates that one entity is permitted or able to borrow something (such as resources, items, or privileges) from 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:13 p.m.