Triple
T8208624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Barras |
E191753
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Barras |
E191753
|
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: Barras | Statement: [Paul Barras, familyName, Barras]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barras Context triple: [Paul Barras, familyName, Barras]
-
A.
Barras
chosen
Barras is a French surname most notably associated with Paul Barras, a leading political figure of the French Revolution and the Directory.
-
B.
Barra
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.
-
C.
Barra
Barra is the surname of Mary Barra, the prominent American business executive and CEO of General Motors.
-
D.
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.
-
E.
Barrera
Barrera is a Spanish-language surname borne by numerous notable individuals, including Mexican boxing champion Marco Antonio Barrera.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dc784881908e1f63ac907cdd01 |
completed | March 31, 2026, 7:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccedda69148190b8c221221de5dae5 |
completed | April 1, 2026, 10:05 a.m. |
Created at: March 30, 2026, 5:43 p.m.