Triple
T37383562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars: Battlefront II |
E928501
|
entity |
| Predicate | hasMicrotransactions |
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: [Star Wars: Battlefront II, hasMicrotransactions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMicrotransactions Context triple: [Star Wars: Battlefront II, hasMicrotransactions, true]
-
A.
hasMonetizationFocus
Indicates that one entity is oriented toward or primarily concerned with generating revenue or financial returns from another entity or activity.
-
B.
supportsPeerToPeerTransactions
Indicates that an entity enables or facilitates direct transactions between peers without requiring an intermediary.
-
C.
hasMIC
Indicates that an entity has a specified Minimum Inhibitory Concentration (MIC) value in relation to an antimicrobial agent.
-
D.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
E.
isFeePaying
Indicates that an entity is required to pay a fee in order to participate in, access, or receive a specified service, resource, or activity.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 3, 2026, 4:16 p.m.