Triple
T8413471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gradius |
E198676
|
entity |
| Predicate | scrollingDirection |
P81862
|
FINISHED |
| Object | horizontal |
—
|
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: horizontal | Statement: [Gradius, scrollingDirection, horizontal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scrollingDirection Context triple: [Gradius, scrollingDirection, horizontal]
-
A.
scanDirection
Indicates the direction or orientation in which a scanning action is performed or data is acquired.
-
B.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
C.
directionalConfiguration
Indicates a specific spatial or directional arrangement that one entity has relative to another.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
scrollPosition
Indicates the current vertical or horizontal offset of a scrollable container relative to its starting position.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e18e7c8190a30b14136dee3d93 |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:06 p.m.