Triple
T28406525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hercules Graphics Card |
E719542
|
entity |
| Predicate | requiresMonitorType |
P138915
|
FINISHED |
| Object | TTL monochrome monitor |
—
|
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: TTL monochrome monitor | Statement: [Hercules Graphics Card, requiresMonitorType, TTL monochrome monitor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresMonitorType Context triple: [Hercules Graphics Card, requiresMonitorType, TTL monochrome monitor]
-
A.
monitoringRequirement
Indicates that one entity is obligated to observe, track, or regularly check another entity or process according to specified criteria or conditions.
-
B.
canBeMonitoredWith
Indicates that one entity is suitable or able to be observed, tracked, or supervised using another specified entity or method.
-
C.
pairedMonitorType
Indicates that one monitor is associated with or linked to another monitor of a specified type as its pair.
-
D.
isMonitored
Indicates that an entity is being actively observed, tracked, or supervised by another entity or system.
-
E.
requiresDisplayType
chosen
Indicates that one entity can only be properly used, rendered, or interpreted when a specific type of display or presentation format is available.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:23 a.m.