Triple
T29182190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Rapid Fire Unit |
E739772
|
entity |
| Predicate | buttonSupport |
P166402
|
FINISHED |
| Object | Button 1 |
—
|
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: Button 1 | Statement: [Sega Rapid Fire Unit, buttonSupport, Button 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buttonSupport Context triple: [Sega Rapid Fire Unit, buttonSupport, Button 1]
-
A.
buttonType
Indicates the specific category or style of a button within a user interface or control set.
-
B.
buttonCount
Indicates the number of buttons associated with or present on a given entity.
-
C.
buttonLabel
Indicates the textual or symbolic label that is displayed on a button to represent its function or purpose.
-
D.
hasButtons
Indicates that an entity possesses one or more buttons as part of its features or design.
-
E.
keySupportFrom
Indicates that one entity provides essential backing, endorsement, or assistance that is crucial for the success or continuation of another entity or action.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66384473c81909fb9ff9037f56b67 |
completed | May 2, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 11:58 a.m.