Triple
T2900402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foreign Legion |
E62639
|
entity |
| Predicate | marchingPace |
P22605
|
FINISHED |
| Object | 88 steps per minute |
—
|
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: 88 steps per minute | Statement: [Foreign Legion, marchingPace, 88 steps per minute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marchingPace Context triple: [Foreign Legion, marchingPace, 88 steps per minute]
-
A.
regimentalMarch
Indicates a coordinated, rhythmic movement of a group in formation, typically following strict timing and alignment as in military drill.
-
B.
regimentalQuickMarch
chosen
Indicates a formal military marching action performed at the standard quick-march pace used in regimental drill and ceremony.
-
C.
regimentalSlowMarch
Indicates a formal, measured marching movement performed at a deliberately slow pace, typically used in regimental or ceremonial military contexts.
-
D.
movementPeriod
Indicates the span of time during which a movement or motion occurs or is valid.
-
E.
movementSpeed
Indicates the rate at which an entity changes its position over time.
- 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_69ab4c3e070c8190b78d3d2c005876dd |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abe0b081308190af8875151fb11c4e |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:10 p.m.