Triple
T37012774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Conservatory |
E915992
|
entity |
| Predicate | controlledByInGame |
P199217
|
FINISHED |
| Object | Abbey of the Everyman |
—
|
NE NERFINISHED |
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: Abbey of the Everyman | Statement: [Royal Conservatory, controlledByInGame, Abbey of the Everyman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByInGame Context triple: [Royal Conservatory, controlledByInGame, Abbey of the Everyman]
-
A.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
B.
isPlayerControlled
Indicates that an entity is currently being directed or controlled by a human player rather than by the system or AI.
-
C.
controlledIn
Indicates that one entity exercised control, authority, or governance over another entity within a specific context or domain.
-
D.
controlledByInStory
Indicates that, within the context of a specific story or narrative, one entity exercises control or authority over another.
-
E.
performedInGame
Indicates that an action or event was carried out during a particular game or match.
- F. None of above. chosen
Provenance (4 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_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
| PDg | Predicate description generation | batch_69ff263632608190a99beb73608066d8 |
completed | May 9, 2026, 12:19 p.m. |
Created at: May 3, 2026, 4:14 p.m.