Triple
T11513893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parade |
E272980
|
entity |
| Predicate | secondaryDistributionChannel |
P99885
|
FINISHED |
| Object | website |
—
|
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: website | Statement: [Parade, secondaryDistributionChannel, website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryDistributionChannel Context triple: [Parade, secondaryDistributionChannel, website]
-
A.
primaryDistribution
Indicates that one entity serves as the main or principal channel through which another entity is distributed or allocated.
-
B.
secondaryCustomer
Indicates a relationship where one customer is designated as an additional or subordinate customer associated with a primary customer in a given context.
-
C.
secondaryHub
Indicates that an entity functions as a secondary or backup hub in relation to a primary hub within a network or system.
-
D.
secondaryTransmissionRoute
Indicates a non-primary pathway or mechanism through which something (such as a disease, signal, or influence) is transmitted from one entity to another.
-
E.
secondaryBrand
Indicates that one brand is a subordinate, supporting, or less prominent brand in relation to a primary brand.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db8bf9c8190820c289e6b0c3873 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.