Triple
T28998043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISPF |
E736219
|
entity |
| Predicate | supportsTerminalType |
P96660
|
FINISHED |
| Object | 3270 terminal |
—
|
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: 3270 terminal | Statement: [ISPF, supportsTerminalType, 3270 terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTerminalType Context triple: [ISPF, supportsTerminalType, 3270 terminal]
-
A.
has terminal type
chosen
Indicates that an entity is associated with a specific terminal type or category it belongs to.
-
B.
supportsTerminalConnections
Indicates that one entity is capable of handling or enabling direct connections to terminal interfaces or endpoints.
-
C.
supportsRemoteTerminal
Indicates that one entity provides or enables access to another entity via a remote terminal interface.
-
D.
supportsMultipleTerminals
Indicates that an entity is capable of handling or operating with more than one terminal or endpoint simultaneously.
-
E.
hasIntegratedTerminal
Indicates that one entity includes or supports a built-in terminal interface as part of its functionality.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a0235be932081908857bc3a77c27e7d |
completed | May 11, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_6a022c865dec81909e02b2f330e987e6 |
completed | May 11, 2026, 7:22 p.m. |
Created at: April 28, 2026, 9:32 a.m.