Triple
T19592761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carillon Berlin |
E470276
|
entity |
| Predicate | isManualPlayable |
P136384
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Carillon Berlin, isManualPlayable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isManualPlayable Context triple: [Carillon Berlin, isManualPlayable, true]
-
A.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
B.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
C.
hasManual
Indicates that an entity is associated with a manual that provides instructions or documentation for it.
-
D.
isUsedToPlay
Indicates that something serves as an instrument, tool, or medium for engaging in a game, sport, or other form of play.
-
E.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64057460c8190962e2e58f06b3985 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:43 p.m.