Triple
T5938502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attari–Wagah border |
E132104
|
entity |
| Predicate | flagLoweringInvolves |
P67028
|
FINISHED |
| Object | synchronized marching |
—
|
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: synchronized marching | Statement: [Attari–Wagah border, flagLoweringInvolves, synchronized marching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagLoweringInvolves Context triple: [Attari–Wagah border, flagLoweringInvolves, synchronized marching]
-
A.
flagUsedIn
Indicates that a particular flag is employed or referenced within a given context, such as a program, configuration, or process.
-
B.
flagUsedBy
Indicates that a particular flag is officially used by a specified entity, such as a country, organization, or group.
-
C.
loweredWhen
Indicates that one entity decreases or is reduced in value, level, or intensity when a specified condition involving another entity holds.
-
D.
flag
Indicates that one entity marks, signals, or draws attention to another entity, often to denote status, importance, or the need for review or action.
-
E.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
- F. None of above. chosen
Provenance (4 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03f26f51881908cc253fe5775a1fc |
completed | March 22, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c03355caf08190b960563a1aed23f9 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03f23dd20819089dbf0de0d913602 |
completed | March 22, 2026, 7:12 p.m. |
Created at: March 22, 2026, 4:01 p.m.