Triple
T27730586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamerscore |
E697419
|
entity |
| Predicate | isDisplayedAlongside |
P4540
|
FINISHED |
| Object | player avatar |
—
|
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: player avatar | Statement: [Gamerscore, isDisplayedAlongside, player avatar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDisplayedAlongside Context triple: [Gamerscore, isDisplayedAlongside, player avatar]
-
A.
appearsAlongside
Indicates that two entities are present or occur together in the same context, setting, or instance.
-
B.
displayedWith
chosen
Indicates that one entity is shown or presented together alongside another entity in the same context or view.
-
C.
isRankedAlongside
Indicates that two or more entities share the same or very similar rank, status, or position within a given ordering or hierarchy.
-
D.
printedAlongside
Indicates that two items are printed together in the same context, such as on the same page, document, or output.
-
E.
isComponentAlongWith
Indicates that an entity functions as a component in conjunction with one or more other components, typically forming a combined or complementary unit within a larger whole.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 3:11 p.m.