Triple
T29363592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halo: Reach |
E744655
|
entity |
| Predicate | hasMultiplayerMaps |
P101541
|
FINISHED |
| Object | Forge World |
—
|
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 World | Statement: [Halo: Reach, hasMultiplayerMaps, Forge World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultiplayerMaps Context triple: [Halo: Reach, hasMultiplayerMaps, Forge World]
-
A.
hasMultiplayerMapEditor
Indicates that the subject includes a map editor feature that can be used by multiple players simultaneously.
-
B.
hasMultiplayer
Indicates that an entity (such as a game or application) supports a mode where multiple users can participate or interact simultaneously.
-
C.
supportsMultiplayerMapSize
Indicates that something (such as a game or system) allows or is compatible with a specific map size when running in multiplayer mode.
-
D.
multiplayerMapsCount
Indicates the number of maps or levels that support multiplayer gameplay within a game or system.
-
E.
multiplayerMap
chosen
Indicates that a map or environment is designed to support gameplay involving multiple players 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 2:20 p.m.