Triple
T9825812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barrow Gang |
E238649
|
entity |
| Predicate | ambushLocation |
P20435
|
FINISHED |
| Object | near Gibsland, Louisiana |
—
|
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: near Gibsland, Louisiana | Statement: [Barrow Gang, ambushLocation, near Gibsland, Louisiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ambushLocation Context triple: [Barrow Gang, ambushLocation, near Gibsland, Louisiana]
-
A.
bombPlacement
Indicates the act of positioning or installing a bomb at a specific location or target.
-
B.
notableAttackLocation
chosen
Indicates the specific place where a significant or notable attack occurred in relation to the subject.
-
C.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
D.
hasPlannedAttackPoint
Indicates that an entity has designated or selected a specific location as the intended site for carrying out an attack.
-
E.
rescuedLocation
Indicates the place where a rescue action occurred or from which someone or something was rescued.
- F. None of above.
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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb32370e8819087c85fb8328587be |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:31 p.m.