Triple
T2189217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attitude and Articulation Control Subsystem computer |
E49821
|
entity |
| Predicate | hardwareGeneration |
P9898
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Attitude and Articulation Control Subsystem computer, hardwareGeneration, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardwareGeneration Context triple: [Attitude and Articulation Control Subsystem computer, hardwareGeneration, 1970s]
-
A.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
B.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
C.
technologyGeneration
chosen
Indicates the generational level or era of technology associated with or used by an entity in relation to another.
-
D.
cpuModel
Indicates the specific processor model associated with a given computing device or system.
-
E.
hasHardwareSeries
Indicates that one hardware item belongs to, or is categorized under, a particular hardware series or product line.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.