Triple
T15756418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GEE |
E381977
|
entity |
| Predicate | operatorDisplay |
P23550
|
FINISHED |
| Object | oscilloscope-type CRT |
—
|
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: oscilloscope-type CRT | Statement: [GEE, operatorDisplay, oscilloscope-type CRT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorDisplay Context triple: [GEE, operatorDisplay, oscilloscope-type CRT]
-
A.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
B.
otherOperator
Indicates a relationship where one operator is distinguished from, or serves as an alternative to, another operator within the same context or system.
-
C.
operatorStyle
Indicates the manner or approach an operator uses to perform or manage an operation, such as their method, technique, or behavioral style in carrying out tasks.
-
D.
operatorPlanned
Indicates that an operator has scheduled or arranged a specific action, process, or operation to occur.
-
E.
displays
chosen
Indicates that one entity visually presents or shows another entity’s content or information.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b1ff4881909d5240d1d30f5c8b |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.