Triple
T29100397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kickstart disk (early Amiga 1000) |
E736624
|
entity |
| Predicate | loadedInto |
P84799
|
FINISHED |
| Object | RAM at startup |
—
|
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: RAM at startup | Statement: [Kickstart disk (early Amiga 1000), loadedInto, RAM at startup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadedInto Context triple: [Kickstart disk (early Amiga 1000), loadedInto, RAM at startup]
-
A.
loadedWith
Indicates that one entity is carrying, filled with, or heavily supplied with another entity.
-
B.
fedInto
chosen
Indicates that something is supplied, channeled, or input from one entity into another as part of a process or flow.
-
C.
loader
Indicates a relationship where an entity is responsible for loading or placing items, data, or resources into another system, container, or context.
-
D.
enteredInto
Indicates that one entity has initiated or become formally involved in a particular state, agreement, relationship, or situation with another entity.
-
E.
enteredIntoBy
Indicates that an agreement, contract, or formal arrangement has been initiated or established by a particular party.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:11 a.m.