Triple
T4161331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Black |
E91539
|
entity |
| Predicate | releaseTypeOfRacer-X |
P3286
|
FINISHED |
| Object | EP |
—
|
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: EP | Statement: [Big Black, releaseTypeOfRacer-X, EP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseTypeOfRacer-X Context triple: [Big Black, releaseTypeOfRacer-X, EP]
-
A.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an entity.
-
B.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
C.
releasedUnderMoniker
Indicates that a work was released using a particular stage name, alias, or alternate moniker rather than the creator’s primary name.
-
D.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
E.
releasedBy
Indicates that something (such as a product, work, or item) is made available, issued, or launched by a particular agent or organization.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.