Triple
T37465995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legend of Solgard |
E931034
|
entity |
| Predicate | supportsMicrotransactions |
P194398
|
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: [Legend of Solgard, supportsMicrotransactions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMicrotransactions Context triple: [Legend of Solgard, supportsMicrotransactions, true]
-
A.
hasMicrotransactions
chosen
Indicates that an item, product, or system includes optional small-scale purchases or payments within its overall experience or usage.
-
B.
supportsTransactions
Indicates that one entity provides the capability for another entity to perform or manage transactions reliably.
-
C.
supportsPeerToPeerTransactions
Indicates that an entity enables or facilitates direct transactions between peers without requiring an intermediary.
-
D.
supportsMobileWallets
Indicates that an entity provides the capability to make or accept payments through mobile wallet services.
-
E.
supportsExchangeBetween
Indicates that one entity enables or facilitates the exchange or transfer of something (e.g., data, value, or resources) between two or more other entities.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.