Triple
T18065637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRN-BRU |
E432285
|
entity |
| Predicate | hasSugarFreeVariant |
P52605
|
FINISHED |
| Object | IRN-BRU XTRA |
—
|
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: IRN-BRU XTRA | Statement: [IRN-BRU, hasSugarFreeVariant, IRN-BRU XTRA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IRN-BRU XTRA Context triple: [IRN-BRU, hasSugarFreeVariant, IRN-BRU XTRA]
-
A.
IRN-BRU
chosen
IRN-BRU is a famous bright orange Scottish carbonated soft drink known for its unique, fruity flavor and iconic status in Scotland’s popular culture.
-
B.
BR2
BR2 is a UK postcode district covering parts of Hayes and surrounding areas in the London Borough of Bromley in southeast England.
-
C.
Brupass
Brupass is an integrated public transport ticketing system that allows seamless travel across multiple operators and modes within the Brussels metropolitan area.
-
D.
BRU
BRU is the IATA airport code for Brussels Airport, the main international airport serving Brussels, Belgium.
-
E.
BRN
BRN is the IATA airport code for Bern Airport, the primary airport serving Switzerland’s capital city.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4cce81de88190bd94d4ccee3e180c |
completed | April 19, 2026, 12:39 p.m. |
Created at: April 10, 2026, 10:26 a.m.