Triple
T5451514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple I |
E122379
|
entity |
| Predicate | originalKitStatus |
P22553
|
FINISHED |
| Object | not sold as a kit, but as assembled board |
—
|
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: not sold as a kit, but as assembled board | Statement: [Apple I, originalKitStatus, not sold as a kit, but as assembled board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalKitStatus Context triple: [Apple I, originalKitStatus, not sold as a kit, but as assembled board]
-
A.
traditionalKit
Indicates that an entity is a conventional or customary set of tools, equipment, or components used together for a particular purpose.
-
B.
materialStatus
Indicates the current state or condition of a material, such as its availability, usage, or processing stage.
-
C.
standardEquipmentOrigin
Indicates that an item’s standard equipment comes from or is originally supplied by a specified source or origin.
-
D.
originalSpireStatus
Indicates the initial or prior condition or classification of a spire before any subsequent changes or updates.
-
E.
kitType
chosen
Indicates the specific category or configuration of a kit associated with an entity or activity.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.