Triple
T11185383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MP 43 |
E264651
|
entity |
| Predicate | developedForCartridgeType |
P91968
|
FINISHED |
| Object | intermediate cartridge |
—
|
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: intermediate cartridge | Statement: [MP 43, developedForCartridgeType, intermediate cartridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedForCartridgeType Context triple: [MP 43, developedForCartridgeType, intermediate cartridge]
-
A.
intendedCartridgeStandard
chosen
Indicates that an item is designed to be used with, or conform to, a particular cartridge standard.
-
B.
cartridge
Indicates that one entity is a cartridge associated with, contained in, or used by another entity.
-
C.
requiresCartridgeSlotOf
Indicates that one entity needs to use or be connected to the cartridge slot provided by another entity in order to function or be compatible.
-
D.
developedForProgram
Indicates that something was created, designed, or produced specifically to be used in or support a particular program.
-
E.
developedSystemFor
Indicates that one entity created or engineered a system intended to be used by or on behalf of another entity.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8abbeac8190ad6e419258999f4e |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.