Triple
T31989629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMI Jericho 941 |
E816827
|
entity |
| Predicate | slideDesign |
P173090
|
FINISHED |
| Object | full-length slide rails |
—
|
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: full-length slide rails | Statement: [IMI Jericho 941, slideDesign, full-length slide rails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slideDesign Context triple: [IMI Jericho 941, slideDesign, full-length slide rails]
-
A.
slideType
Indicates the specific category or kind of slide associated with an item or presentation element.
-
B.
menuDesign
Indicates the relationship in which one entity defines or specifies the layout, structure, or visual arrangement of another entity’s menu.
-
C.
coverDesign
Indicates that one entity is responsible for creating or specifying the visual design of another entity’s cover (such as a book, album, or publication).
-
D.
helpsDesign
Indicates that one entity assists or contributes to another entity’s design or design process.
-
E.
playDesignFeature
Indicates that a design feature is incorporated into or utilized within a play or gameplay experience.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3b3c128819088fbbf04ffb3b3ec |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:13 a.m.