Triple
T36632936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joachim |
E904376
|
entity |
| Predicate | isPlayableIn |
P88329
|
FINISHED |
| Object | Parabola |
—
|
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: Parabola | Statement: [Joachim, isPlayableIn, Parabola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlayableIn Context triple: [Joachim, isPlayableIn, Parabola]
-
A.
playableInGame
chosen
Indicates that something can be used or controlled as an active element within a particular game.
-
B.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
C.
canAlsoBePlayedIn
Indicates that something (such as a game, media, or activity) is additionally playable or usable in another context, format, or environment beyond its primary one.
-
D.
isPlayedUnder
Indicates that an activity, game, or performance occurs while subject to specific rules, conditions, or circumstances defined by another entity.
-
E.
isInPlayBy
Indicates that an entity is currently active or participating within a game, scenario, or context as a result of actions taken by a specific agent or player.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.