Triple
T18000476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Englishman in New York |
E430612
|
entity |
| Predicate | remixNotableVersion |
P66064
|
FINISHED |
| Object | Ben Liebrand remix |
—
|
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: Ben Liebrand remix | Statement: [Englishman in New York, remixNotableVersion, Ben Liebrand remix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remixNotableVersion Context triple: [Englishman in New York, remixNotableVersion, Ben Liebrand remix]
-
A.
notableRemixBy
chosen
Indicates that one creative work has a particularly recognized or significant remix created by a specified artist or entity.
-
B.
notableVersionType
Indicates that one version of an entity is recognized as particularly significant or noteworthy relative to other versions.
-
C.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
D.
notableFork
Indicates that one entity is a significant fork or derivative version of another, typically diverging in a notable or influential way from the original.
-
E.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e82ca48190aeb53e03c95ef223 |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.