Triple
T35407812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Round and Around |
E1023413
|
entity |
| Predicate | hasOriginalReleaseTerritory |
P33718
|
FINISHED |
| Object | United Kingdom |
E732
|
NE 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: United Kingdom | Statement: [Round and Around, hasOriginalReleaseTerritory, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalReleaseTerritory Context triple: [Round and Around, hasOriginalReleaseTerritory, United Kingdom]
-
A.
originalTerritory
Indicates that a specified area or region is the initial or historically established domain associated with an entity before any changes, transfers, or expansions.
-
B.
countryOfFirstRelease
chosen
Indicates the country in which a work (such as a film, game, or product) was first officially released.
-
C.
reReleasedInCountry
Indicates that a previously released work was released again in a specified country.
-
D.
hasOriginalCountryTitle
Indicates that an entity is associated with the title it originally had in its country of origin.
-
E.
countryOfRelease
Indicates the country in which an item (such as a product, work, or media) was officially released.
- F. None of above.
Provenance (4 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38369ab8f881908d46272214d26df3 |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 3, 2026, 4:03 p.m.