Triple
T21268859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple DOS |
E524201
|
entity |
| Predicate | supportsApplesoftBASICPrograms |
P143449
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Apple DOS, supportsApplesoftBASICPrograms, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsApplesoftBASICPrograms Context triple: [Apple DOS, supportsApplesoftBASICPrograms, true]
-
A.
supportsMultitaskingOfDOSPrograms
Indicates that a system or environment is capable of running and managing multiple DOS programs simultaneously.
-
B.
isAmigaCompatible
Indicates that something is capable of operating with or supporting the hardware, software, or standards of the Amiga computer platform.
-
C.
supports64BitApps
Indicates that the subject is capable of running or is compatible with 64-bit applications.
-
D.
supportsSIMInstruction
Indicates that one entity is capable of handling or executing a specified SIM (Subscriber Identity Module) instruction for another entity.
-
E.
supportsProgramOf
Indicates that one entity provides assistance, resources, or endorsement to help another entity’s program operate or succeed.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73651115081908b5083ba818a6bb1 |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 4:01 p.m.