Triple
T5351684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolver |
E102591
|
entity |
| Predicate | labelRegion |
P63197
|
FINISHED |
| Object | UK release on Parlophone |
—
|
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: UK release on Parlophone | Statement: [Revolver, labelRegion, UK release on Parlophone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelRegion Context triple: [Revolver, labelRegion, UK release on Parlophone]
-
A.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
B.
latitudeRegion
Indicates that an entity is located within, or associated with, a specific geographic region defined by latitude coordinates.
-
C.
regionName
Indicates the name assigned to a specific geographic or administrative region.
-
D.
mentionsRegion
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
-
E.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
- F. None of above. chosen
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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd861188ac81908ef2b1f25cc6c864 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd85e69e808190b29548670fd2900a |
completed | March 20, 2026, 5:37 p.m. |
Created at: March 20, 2026, 2:01 p.m.