Triple
T29195403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halo 5: Guardians |
E740109
|
entity |
| Predicate | hasMultiplayerMapEditor |
P182232
|
FINISHED |
| Object | Forge |
—
|
NE NERFINISHED |
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: Forge | Statement: [Halo 5: Guardians, hasMultiplayerMapEditor, Forge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultiplayerMapEditor Context triple: [Halo 5: Guardians, hasMultiplayerMapEditor, Forge]
-
A.
multiplayerMap
Indicates that a map or environment is designed to support gameplay involving multiple players simultaneously.
-
B.
supportsMultiplayerMapSize
Indicates that something (such as a game or system) allows or is compatible with a specific map size when running in multiplayer mode.
-
C.
hasMultiplayer
Indicates that an entity (such as a game or application) supports a mode where multiple users can participate or interact simultaneously.
-
D.
multiplayerMapType
Indicates the type or category of map used in a multiplayer context (e.g., game mode layout or environment style).
-
E.
multiplayerMapCountAtLaunch
Indicates the number of multiplayer maps that are available when the game is first launched.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 28, 2026, 12:04 p.m.