Triple
T27543256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Link Up & Suede |
E695292
|
entity |
| Predicate | includesProductionBy |
P26032
|
FINISHED |
| Object | Knxwledge |
—
|
NE NERFINISHED |
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: Knxwledge | Statement: [Link Up & Suede, includesProductionBy, Knxwledge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesProductionBy Context triple: [Link Up & Suede, includesProductionBy, Knxwledge]
-
A.
includesProduce
Indicates that one entity contains or offers certain produce items as part of its contents, inventory, or offerings.
-
B.
requiresProductionWithin
Indicates that one entity’s fulfillment or validity depends on another entity being produced within a specified time frame or contextual boundary.
-
C.
hasProduction
chosen
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
D.
inProduction
Indicates that something is currently being created, manufactured, or developed but is not yet completed or released.
-
E.
isProducedFrom
Indicates that something is created, generated, or derived from a specified source or input.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 27, 2026, 1:32 p.m.