Triple
T29676777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illegal Records |
E750838
|
entity |
| Predicate | releasedMaterialFor |
P138774
|
FINISHED |
| Object | The Police |
—
|
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: The Police | Statement: [Illegal Records, releasedMaterialFor, The Police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedMaterialFor Context triple: [Illegal Records, releasedMaterialFor, The Police]
-
A.
releasedMaterialBy
chosen
Indicates that a material, product, or content item has been officially released, issued, or made available by a particular agent or organization.
-
B.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
-
C.
materialReleased
Indicates that a material has been emitted, discharged, or otherwise released from its source into an environment or system.
-
D.
releasedInsteadOf
Indicates that one entity was released in place of, or as a substitute for, another entity that was not released.
-
E.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 7:07 p.m.