Triple
T29363633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halo: The Master Chief Collection |
E744656
|
entity |
| Predicate | pcDistributor |
P1951
|
FINISHED |
| Object | Steam |
—
|
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: Steam | Statement: [Halo: The Master Chief Collection, pcDistributor, Steam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pcDistributor Context triple: [Halo: The Master Chief Collection, pcDistributor, Steam]
-
A.
distributorType
Indicates the specific category or role of a distributor in relation to the distribution of a product or service.
-
B.
distributor
chosen
Indicates that an entity is responsible for supplying, delivering, or making another entity’s products or materials available to others.
-
C.
distributesFrom
Indicates that something acts as the source or origin from which items, resources, or information are distributed to others.
-
D.
computerSystemProvider
Indicates that one entity supplies, operates, or is responsible for providing a computer system to another entity.
-
E.
distributorContext
Indicates the contextual relationship in which a distributor operates or is relevant to a particular entity, transaction, or scenario.
- 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_69f6698a5c608190b80127eb9605ab60 |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:20 p.m.