Triple
T29912378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCKeyboard |
E759699
|
entity |
| Predicate | hasAssociatedClass |
P25008
|
FINISHED |
| Object | GCKeyboardInput |
—
|
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: GCKeyboardInput | Statement: [GCKeyboard, hasAssociatedClass, GCKeyboardInput]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedClass Context triple: [GCKeyboard, hasAssociatedClass, GCKeyboardInput]
-
A.
hasAssociatedType
Indicates that one entity is linked to another entity that specifies its type, category, or classification.
-
B.
associatedWithClass
chosen
Indicates that an entity has a connection or linkage to a particular class or category, without specifying the exact nature of that relationship.
-
C.
hasCanonicalAssociation
Indicates that one entity is formally recognized as the standard or authoritative counterpart associated with another entity.
-
D.
hasPrimaryAssociation
Indicates that one entity is chiefly or most directly connected, linked, or related to another among possible associations.
-
E.
hasDimensionAssociation
Indicates an association between an entity and one or more of its dimensions, such as size, length, width, height, or other measurable extents.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 6:10 p.m.