Triple
T37461023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y’Shaarj, Rage Unbound |
E930915
|
entity |
| Predicate | canBeGenerated |
P187890
|
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: [Y’Shaarj, Rage Unbound, canBeGenerated, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeGenerated Context triple: [Y’Shaarj, Rage Unbound, canBeGenerated, Yes]
-
A.
canGenerateOn
Indicates that one entity has the capability to produce or create another entity specifically on or within a particular medium, platform, or context.
-
B.
canBeCreatedFor
Indicates that one entity is eligible or allowed to be created in association with, or on behalf of, another entity.
-
C.
isGenerated
chosen
Indicates that one entity is produced, created, or brought into existence as a result of another entity or process.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
canBeConstructedWith
Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
- 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_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: May 3, 2026, 4:17 p.m.