Triple
T38634604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highrise |
E937543
|
entity |
| Predicate | designedForPlaystyle |
P9494
|
FINISHED |
| Object | snipers |
—
|
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: snipers | Statement: [Highrise, designedForPlaystyle, snipers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForPlaystyle Context triple: [Highrise, designedForPlaystyle, snipers]
-
A.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
B.
playstyleBenefit
Indicates that one playstyle provides an advantage, improvement, or positive effect to a player or entity.
-
C.
playstyleWeakness
Indicates a relationship where one playstyle is particularly vulnerable or disadvantaged when facing another playstyle.
-
D.
dedicatedToStyleOf
Indicates that something is devoted or specifically tailored to a particular style or manner of expression.
-
E.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
Created at: May 3, 2026, 4:32 p.m.