Triple
T33434776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamepad API |
E856214
|
entity |
| Predicate | earlyImplementationsAppearedIn |
P27494
|
FINISHED |
| Object | Firefox |
—
|
NE NERFINISHED |
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: Firefox | Statement: [Gamepad API, earlyImplementationsAppearedIn, Firefox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyImplementationsAppearedIn Context triple: [Gamepad API, earlyImplementationsAppearedIn, Firefox]
-
A.
historicallyImplementedIn
chosen
Indicates that an action, practice, or system was carried out or put into effect in a particular place or context during a past historical period.
-
B.
firstImplementedBy
Indicates that the subject was initially realized, executed, or put into practice by the specified agent or entity.
-
C.
dateImplemented
Indicates the date on which something (such as a plan, rule, feature, or system) was put into effect or made operational.
-
D.
initialReleaseApprox
Indicates that an entity’s first release or debut occurred around an estimated or approximate point in time rather than on a precisely known date.
-
E.
historicallyImplementedAs
Indicates that one entity was used or realized as another entity in the past, even if that is no longer the case.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:36 a.m.