Triple
T30568517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Number Seventeen (1932 film) |
E778054
|
entity |
| Predicate | releaseLocation |
P180888
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Number Seventeen (1932 film), releaseLocation, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseLocation Context triple: [Number Seventeen (1932 film), releaseLocation, United Kingdom]
-
A.
releasePlace
chosen
Indicates the location where an entity is released, issued, or made publicly available.
-
B.
releaseRegion
Indicates the geographic or jurisdictional area in which something (such as a product, service, or content) is made available or officially released.
-
C.
releaseType
Indicates the kind or category of a release event or version associated with an entity.
-
D.
releasedUnder
Indicates that one entity is made available, distributed, or published according to the terms, conditions, or authority specified by another entity (such as a license, label, or governing framework).
-
E.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 29, 2026, 8:21 p.m.