Triple
T33749266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The CW |
E864790
|
entity |
| Predicate | notableProgrammingBrand |
P108990
|
FINISHED |
| Object | Arrowverse |
E237380
|
NE 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: Arrowverse | Statement: [The CW, notableProgrammingBrand, Arrowverse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProgrammingBrand Context triple: [The CW, notableProgrammingBrand, Arrowverse]
-
A.
programmingBrand
chosen
Indicates a relationship where a brand is associated with, specializes in, or is recognized for programming-related products, services, or activities.
-
B.
notableProgrammingCategory
Indicates that an entity is recognized as belonging to a significant or distinguished category within the domain of programming.
-
C.
notableProgramming
Indicates that an entity is notably associated with programming, such as being recognized for significant work, skill, or contributions in the field of programming.
-
D.
hasBrandRecognitionFor
Indicates that one entity is aware of, recognizes, or can identify the brand of another entity.
-
E.
notableApplicationDevelopedOn
Indicates that a notable software application was created or built to run on a particular platform, system, or technology.
- F. None of above.
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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a365c8e75d081908da58c410eb3017d |
completed | June 20, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:45 a.m.