Triple
T21673796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Hits (High Tide and Green Grass) |
E534916
|
entity |
| Predicate | hasDifferentUSAndUKVersions |
P102626
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Big Hits (High Tide and Green Grass), hasDifferentUSAndUKVersions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDifferentUSAndUKVersions Context triple: [Big Hits (High Tide and Green Grass), hasDifferentUSAndUKVersions, true]
-
A.
hasUKVersion
chosen
Indicates that an entity has a corresponding version or variant that is specific to the United Kingdom.
-
B.
hasInternationalVersion
Indicates that an entity has a corresponding version or counterpart adapted for use in multiple countries or international contexts.
-
C.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
-
D.
hasDifferentVersion
Indicates that one entity exists as a version that differs in some way from another entity.
-
E.
hasMultipleVersions
Indicates that an entity exists in more than one distinct version or revision.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0e06688190a75ea29534f5eed3 |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:41 p.m.