Triple
T35407817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Round and Around |
E1023413
|
entity |
| Predicate | isHitIn |
P155157
|
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: [Round and Around, isHitIn, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHitIn Context triple: [Round and Around, isHitIn, United Kingdom]
-
A.
isMajorHitIn
Indicates that a work (such as a song, film, or product) achieved major commercial success or popularity within a specified market, region, or context.
-
B.
wasAHitIn
chosen
Indicates that something (such as a work, product, or performance) achieved notable success or popularity within a specified context, time period, or location.
-
C.
isClubHit
Indicates that an entity is struck or impacted by a club in an action or event.
-
D.
isTargetIn
Indicates that a specified entity lies within, or is contained inside, a given target region, set, or scope.
-
E.
isEarlyHitFor
Indicates that one entity is an initial or precursor success, discovery, or recognition that occurs early in relation to 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7956423b481908041090133ac61de |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.