Triple
T29057742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PC-8801 |
E735435
|
entity |
| Predicate | primaryDisplay |
P5099
|
FINISHED |
| Object | CRT 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: CRT monitor | Statement: [PC-8801, primaryDisplay, CRT monitor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDisplay Context triple: [PC-8801, primaryDisplay, CRT monitor]
-
A.
primaryView
Indicates that one view or representation is designated as the main or default perspective among multiple possible views of the same entity or content.
-
B.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
C.
primaryInterface
chosen
Indicates that one entity serves as the main or default interface through which another entity is accessed or interacted with.
-
D.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
E.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a00b03a50a88190bfb95cdcfc6142a2 |
completed | May 10, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_6a00afe55f248190b2cb4c7e62cc3ffc |
completed | May 10, 2026, 4:18 p.m. |
Created at: April 28, 2026, 10:12 a.m.