Triple
T37012798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Conservatory |
E915992
|
entity |
| Predicate | supportsPlaystyles |
P192035
|
FINISHED |
| Object | non-lethal approach |
—
|
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: non-lethal approach | Statement: [Royal Conservatory, supportsPlaystyles, non-lethal approach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPlaystyles Context triple: [Royal Conservatory, supportsPlaystyles, non-lethal approach]
-
A.
supportsGameStyle
chosen
Indicates that one entity is compatible with or able to accommodate a particular game style or mode of play.
-
B.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
C.
supportsPlayers
Indicates that an entity provides compatibility or functionality for one or more players to participate or be used.
-
D.
playstyleBenefit
Indicates that one playstyle provides an advantage, improvement, or positive effect to a player or entity.
-
E.
supportsStarPlayers
Indicates that one entity provides assistance, resources, or backing specifically to star or top-performing players.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.