Triple
T27509717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cooke and Wheatstone telegraph |
E694374
|
entity |
| Predicate | displayLayout |
P79764
|
FINISHED |
| Object | grid of letters indicated by crossing needles |
—
|
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: grid of letters indicated by crossing needles | Statement: [Cooke and Wheatstone telegraph, displayLayout, grid of letters indicated by crossing needles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displayLayout Context triple: [Cooke and Wheatstone telegraph, displayLayout, grid of letters indicated by crossing needles]
-
A.
displayType
Indicates the manner or format in which something is presented, shown, or rendered.
-
B.
displayMode
Indicates how content or information is visually presented or arranged to the user.
-
C.
displayConfiguration
chosen
Indicates a relationship where one entity defines or presents the arrangement, layout, or settings used to visually display another entity.
-
D.
displays
Indicates that one entity visually presents or shows another entity’s content or information.
-
E.
displayStructure
Indicates that one entity presents or reveals the internal organization, layout, or arrangement of another entity.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ef858008190bda723fb47853dce |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:15 p.m.