Triple
T1832381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EV3 Intelligent Brick |
E40787
|
entity |
| Predicate | hasDisplay |
P5731
|
FINISHED |
| Object | monochrome LCD display |
—
|
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: monochrome LCD display | Statement: [EV3 Intelligent Brick, hasDisplay, monochrome LCD display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisplay Context triple: [EV3 Intelligent Brick, hasDisplay, monochrome LCD display]
-
A.
hasDisplayType
chosen
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
B.
displayedWith
Indicates that one entity is shown or presented together alongside another entity in the same context or view.
-
C.
displays
Indicates that one entity visually presents or shows another entity’s content or information.
-
D.
hasReplicaDisplays
Indicates that an entity features or presents one or more replica items as displays.
-
E.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
- 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb45402688190b9a535b14030c354 |
completed | March 7, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69abafd6a9948190ac2b2743db6f8f69 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:32 p.m.