Triple
T32562868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QWERTY keyboard layout |
E832274
|
entity |
| Predicate | topRowSequence |
P174598
|
FINISHED |
| Object | QWERTY |
—
|
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: QWERTY | Statement: [QWERTY keyboard layout, topRowSequence, QWERTY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topRowSequence Context triple: [QWERTY keyboard layout, topRowSequence, QWERTY]
-
A.
topForward
Indicates that one entity is positioned or oriented in front of and above another entity along a forward-facing direction.
-
B.
topHas
Indicates that one entity possesses, contains, or is associated with another entity at the highest or most general level in a hierarchy or structure.
-
C.
topLevel
Indicates that an entity occupies the highest or outermost level in a hierarchy, structure, or organizational arrangement, with no parent above it.
-
D.
topBoundary
Indicates that one entity serves as the uppermost limit, edge, or border of another entity or region.
-
E.
topStructure
Indicates that one structure occupies the highest or most superior position relative to other structures within a given system or hierarchy.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c609f1c08190830b42dc4df5ab8d |
completed | May 3, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:03 a.m.