Triple
T9115405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collateral Murder video release |
E218707
|
entity |
| Predicate | fullVersionLength |
P81758
|
FINISHED |
| Object | approximately 39 minutes |
—
|
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: approximately 39 minutes | Statement: [Collateral Murder video release, fullVersionLength, approximately 39 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullVersionLength Context triple: [Collateral Murder video release, fullVersionLength, approximately 39 minutes]
-
A.
longVersionLength
Indicates that one entity specifies the length or duration of a more detailed or extended version of another entity.
-
B.
singleVersionLength
chosen
Indicates the length or duration associated with a single version of something (e.g., an item, product, or media instance).
-
C.
identifierLength
Indicates the length or number of characters in an entity’s identifier.
-
D.
albumVersionLength
Indicates the duration or running time of a specific version of an album.
-
E.
secondFullVersionReference
Indicates that an entity refers to a second complete or fully detailed version of another entity.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a1340881909dc791b825e87ef2 |
completed | April 1, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.