Triple
T29306616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halo Infinite |
E743111
|
entity |
| Predicate | multiplayerStatus |
P80143
|
FINISHED |
| Object | free-to-play |
—
|
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: free-to-play | Statement: [Halo Infinite, multiplayerStatus, free-to-play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiplayerStatus Context triple: [Halo Infinite, multiplayerStatus, free-to-play]
-
A.
playerStatus
Indicates the current state or condition of a player within a game or system, such as their activity, health, or participation status.
-
B.
multiplayerType
chosen
Indicates the type or mode of multiplayer interaction supported between participants.
-
C.
multiplayerModeSharedWith
Indicates that a multiplayer mode is made available or shared from one entity to another for joint use or participation.
-
D.
multiplayerFeature
Indicates that the subject supports or involves multiple users participating together, typically at the same time within the same activity or environment.
-
E.
hasMultiplayer
Indicates that an entity (such as a game or application) supports a mode where multiple users can participate or interact simultaneously.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 1:14 p.m.