Triple
T30421339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noki |
E773907
|
entity |
| Predicate | interactionWithPlayer |
P131174
|
FINISHED |
| Object | provide information |
—
|
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: provide information | Statement: [Noki, interactionWithPlayer, provide information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionWithPlayer Context triple: [Noki, interactionWithPlayer, provide information]
-
A.
heroInteraction
Indicates an interaction or engagement occurring between a hero and another entity, such as assisting, confronting, or collaborating.
-
B.
interactionWithLiving
chosen
Indicates a relationship in which an entity engages in some form of contact, communication, or mutual influence with a living being.
-
C.
interactionWithHumans
Indicates a relationship where an entity engages in some form of contact, communication, or mutual influence with humans.
-
D.
toyGameInteraction
Indicates an interaction where an entity engages with a toy or game, such as playing with, manipulating, or otherwise using it.
-
E.
typicalInteraction
Indicates the usual or most common way in which two entities interact or relate to each other.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 29, 2026, 8:06 p.m.