Triple
T37633022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Boondock Saints |
E936406
|
entity |
| Predicate | mediaTypeConnection |
P125057
|
FINISHED |
| Object | film-related band |
—
|
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: film-related band | Statement: [The Boondock Saints, mediaTypeConnection, film-related band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaTypeConnection Context triple: [The Boondock Saints, mediaTypeConnection, film-related band]
-
A.
mediaTypeAssociation
chosen
Indicates an association between an entity and a specific type or category of media with which it is related or represented.
-
B.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
C.
mediaTypeOrigin
Indicates the original source or context from which a particular media type was derived or introduced.
-
D.
mediaReferenceType
Indicates the specific kind of relationship or role that a referenced media item has in relation to another entity or context.
-
E.
mediaTypeAvailable
Indicates that a particular type or format of media is available for use, access, or distribution in the given context.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:18 p.m.