Triple
T38464294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pura |
E912524
|
entity |
| Predicate | controlTypeInPlatformers |
P199996
|
FINISHED |
| Object | rideable animal companion |
—
|
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: rideable animal companion | Statement: [Pura, controlTypeInPlatformers, rideable animal companion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlTypeInPlatformers Context triple: [Pura, controlTypeInPlatformers, rideable animal companion]
-
A.
controlsType
Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of another entity.
-
B.
controllerShape
Indicates that one entity has the specified geometric or physical form used as a controller in an interaction or system.
-
C.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
D.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
E.
controlInteraction
Indicates an interaction in which one entity directs, regulates, or constrains the behavior or state of another.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
| PDg | Predicate description generation | batch_69ff691e86d0819099fdb5eca5a95632 |
completed | May 9, 2026, 5:04 p.m. |
Created at: May 3, 2026, 4:31 p.m.