Triple
T38593789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonic Arrow |
E932514
|
entity |
| Predicate | informationProvided |
P96146
|
FINISHED |
| Object | enemy silhouettes |
—
|
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: enemy silhouettes | Statement: [Sonic Arrow, informationProvided, enemy silhouettes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationProvided Context triple: [Sonic Arrow, informationProvided, enemy silhouettes]
-
A.
providedInformationTo
Indicates that one entity has supplied or communicated information to another entity.
-
B.
providedInformationOn
chosen
Indicates that one entity supplied or communicated specific information or details to another entity.
-
C.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
D.
requiredInformation
Indicates that certain data or details are necessary and must be provided for a process, action, or relationship to proceed or be valid.
-
E.
informationUsedIn
Indicates that certain information is utilized or applied within a particular context, process, or entity.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.