Triple
T9908565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barra Isles |
E185079
|
entity |
| Predicate | hasMainIsland |
P756
|
FINISHED |
| Object | Barra |
E19026
|
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: Barra | Statement: [Barra Isles, hasMainIsland, Barra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barra Context triple: [Barra Isles, hasMainIsland, Barra]
-
A.
Barra
chosen
Barra is a scenic island in the Outer Hebrides of Scotland, known for its rugged coastline, Gaelic culture, and the unique beach runway at Barra Airport.
-
B.
Barra
Barra is the surname of Mary Barra, the prominent American business executive and CEO of General Motors.
-
C.
La Barra
La Barra is a popular seaside resort town in Uruguay known for its beaches, nightlife, and proximity to Punta del Este.
-
D.
La Barra
La Barra is the natural volcanic reef that shelters Las Canteras Beach in Las Palmas de Gran Canaria, creating its calm, protected waters.
-
E.
De Barra
De Barra is a variant form of the name Barra, typically used as a surname or family name in Irish and Scottish contexts.
- 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb50feb008190aa9c084f590c0ebd |
completed | April 2, 2026, 12:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d23d22c56081909c3e4b8ca0e81fe7 |
completed | April 5, 2026, 10:44 a.m. |
Created at: March 30, 2026, 8:41 p.m.