Triple
T31202513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rifles |
E795511
|
entity |
| Predicate | hasRegimentalSlowMarch |
P22606
|
FINISHED |
| Object | Keel Row |
—
|
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: Keel Row | Statement: [The Rifles, hasRegimentalSlowMarch, Keel Row]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegimentalSlowMarch Context triple: [The Rifles, hasRegimentalSlowMarch, Keel Row]
-
A.
hasRegimentalMarch
Indicates that a military unit or regiment is associated with a specific official march or marching song.
-
B.
regimentalSlowMarch
chosen
Indicates a formal, measured marching movement performed at a deliberately slow pace, typically used in regimental or ceremonial military contexts.
-
C.
hasRegimentalMusic
Indicates that an entity possesses or is associated with a specific set or tradition of regimental music.
-
D.
regimentalMarch
Indicates a coordinated, rhythmic movement of a group in formation, typically following strict timing and alignment as in military drill.
-
E.
regimentalQuickMarch
Indicates a formal military marching action performed at the standard quick-march pace used in regimental drill and ceremony.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
Created at: April 29, 2026, 9:09 p.m.