Triple
T1323827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARPANET Interface Message Processor platform |
E28280
|
entity |
| Predicate | usedOperatingSystem |
P1593
|
FINISHED |
| Object | custom real-time executive |
—
|
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: custom real-time executive | Statement: [ARPANET Interface Message Processor platform, usedOperatingSystem, custom real-time executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOperatingSystem Context triple: [ARPANET Interface Message Processor platform, usedOperatingSystem, custom real-time executive]
-
A.
operatesSystem
Indicates that an entity actively controls, manages, or runs a particular system.
-
B.
operatingSystem
chosen
Indicates that one entity is the operating system running on, or used by, another entity.
-
C.
usedByOperatingSystems
Indicates that something (such as a component, standard, or feature) is utilized or supported by one or more operating systems.
-
D.
primaryOperatingEnvironment
Indicates the main environment, platform, or context in which an entity is primarily designed to operate or function.
-
E.
currentSystem
Indicates that an entity is the system or configuration that is presently active or in use.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19caa148190a1f5be734b7d9005 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.