Triple
T9386110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Rim film franchise |
E225908
|
entity |
| Predicate | subsequentDistributionFormat |
P50239
|
FINISHED |
| Object | home video |
—
|
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: home video | Statement: [Pacific Rim film franchise, subsequentDistributionFormat, home video]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentDistributionFormat Context triple: [Pacific Rim film franchise, subsequentDistributionFormat, home video]
-
A.
subsequentReleaseFormat
chosen
Indicates that one media release is issued in a different format that chronologically follows an earlier release of the same content.
-
B.
laterDistributedOn
Indicates that something was distributed or made available at a time later than a referenced distribution or event date.
-
C.
distributedFormat
Indicates that an entity is made available or disseminated in a particular format or medium.
-
D.
subsequentForm
Indicates that one form, version, or state of something occurs later in sequence or development than another.
-
E.
typicalReleaseFormat
Indicates the usual or standard format in which something is released or published.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d3964c8190b0353f56df755db8 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.