Triple
T10950987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Rothosen |
E258724
|
entity |
| Predicate | refersToKitElement |
P96799
|
FINISHED |
| Object | red shorts |
—
|
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: red shorts | Statement: [Die Rothosen, refersToKitElement, red shorts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToKitElement Context triple: [Die Rothosen, refersToKitElement, red shorts]
-
A.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
-
B.
refersToPort
Indicates that one entity designates, points to, or is associated with a specific port (such as a network, hardware, or logical port).
-
C.
refersToPosition
Indicates that one entity makes reference to, or is associated with, a specific position or location of another entity.
-
D.
PatrickElementReference
Indicates a reference relationship in which one element is linked to or points to another element associated with Patrick.
-
E.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770fc156c8190826e124c13ce7242 |
completed | April 9, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.