Triple
T7087822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steam |
E165120
|
entity |
| Predicate | hasAccountSystem |
P1077
|
FINISHED |
| Object | Steam account |
—
|
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: Steam account | Statement: [Steam, hasAccountSystem, Steam account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccountSystem Context triple: [Steam, hasAccountSystem, Steam account]
-
A.
hasUserService
chosen
Indicates that an entity is associated with or utilizes a particular user-related service.
-
B.
hasRegisterSystem
Indicates that an entity uses or is associated with a particular register system (e.g., a system for recording, tracking, or registering items, events, or participants).
-
C.
supportsSeparateAccounts
Indicates that one entity enables or allows the use or management of distinct, individually maintained accounts rather than a single shared account.
-
D.
hasPASystem
Indicates that an entity possesses or is equipped with a public address (PA) system.
-
E.
hasUser
Indicates that an entity is associated with or linked to a specific user.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e52d26f08190917e5e13b181bdae |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.