Triple
T7894629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VAX |
E183315
|
entity |
| Predicate | hasCompatibilityMode |
P79622
|
FINISHED |
| Object | PDP-11 compatibility mode |
—
|
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: PDP-11 compatibility mode | Statement: [VAX, hasCompatibilityMode, PDP-11 compatibility mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompatibilityMode Context triple: [VAX, hasCompatibilityMode, PDP-11 compatibility mode]
-
A.
checksCompatibilityWith
Indicates that one entity evaluates whether it is compatible or can function harmoniously with another entity.
-
B.
compatibilityModel
Indicates that one entity is defined or evaluated according to a specific compatibility framework, standard, or model in relation to another entity.
-
C.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
D.
hasSoftwareCompatibilityWith
Indicates that one software system can operate correctly and effectively with another software system, without conflicts or required modifications.
-
E.
isGenerallyCompatibleWith
Indicates that two entities can typically function or coexist together without significant conflict, issues, or need for special adaptation.
- F. None of above. chosen
Provenance (4 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a15a7e88190a05474844817e5d2 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 5:01 p.m.