Triple
T15133007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slide Around |
E361467
|
entity |
| Predicate | distributedBy |
P1951
|
FINISHED |
| Object | AWAL |
E507341
|
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: AWAL | Statement: [Slide Around, distributedBy, AWAL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AWAL Context triple: [Slide Around, distributedBy, AWAL]
-
A.
AWAL
chosen
AWAL is a music distribution and services company that supports independent artists with digital releases, marketing, and data-driven promotion.
-
B.
AW
AW is the two-letter ISO 3166-1 alpha-2 country code assigned to Aruba.
-
C.
AW
AW is a German vehicle registration code associated with the district that includes the town of Remagen in the state of Rhineland-Palatinate.
-
D.
AW
AW is the standard abbreviation for Atlantic Water, the relatively warm, salty water mass originating in the North Atlantic that influences ocean circulation and Arctic climate.
-
E.
WAW
WAW is the three-letter IATA airport code for Warsaw Chopin Airport, the primary international airport serving Warsaw, Poland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b29a4c819087f8818e3f5788f5 |
completed | April 15, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feb7fd3c448190b4b06fdc1ab2c6a7 |
completed | May 9, 2026, 4:28 a.m. |
Created at: April 10, 2026, 3:06 a.m.