Triple
T29102018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radiant Silvergun |
E736659
|
entity |
| Predicate | hasOnlineFeatures |
P95527
|
FINISHED |
| Object | online leaderboards (Xbox 360) |
—
|
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: online leaderboards (Xbox 360) | Statement: [Radiant Silvergun, hasOnlineFeatures, online leaderboards (Xbox 360)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineFeatures Context triple: [Radiant Silvergun, hasOnlineFeatures, online leaderboards (Xbox 360)]
-
A.
hasOnlineProvision
chosen
Indicates that an entity offers or supports a service, feature, or function through an online or internet-based channel.
-
B.
hasOnsiteFeature
Indicates that one entity possesses or includes a particular feature that is physically present at its location or premises.
-
C.
hasOnlineCatalog
Indicates that an entity provides a catalog of its items or offerings that is accessible via the internet.
-
D.
hasOnlineTools
Indicates that an entity provides or includes tools or functionalities that are accessible via the internet.
-
E.
hasFrontLineFeature
Indicates that an entity possesses a specific characteristic or element located on its front side or leading edge.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 11:12 a.m.