Triple
T246999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic Day (India) |
E5058
|
entity |
| Predicate | flagHoistingBy |
P6935
|
FINISHED |
| Object | President of India at Kartavya Path |
—
|
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: President of India at Kartavya Path | Statement: [Republic Day (India), flagHoistingBy, President of India at Kartavya Path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagHoistingBy Context triple: [Republic Day (India), flagHoistingBy, President of India at Kartavya Path]
-
A.
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.
-
B.
flagFlown
chosen
Indicates that a particular flag is being displayed or flown at a specific location or by a specific entity.
-
C.
flagBearer
Indicates that one entity serves as the carrier or holder of a flag on behalf of another entity, group, or cause.
-
D.
flagDesigner
Indicates that one entity is the person or group responsible for designing the flag associated with another entity.
-
E.
nationalFlag
Indicates that one entity is the official national flag representing the other entity (a country or nation).
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d13b8088190a3f48f0388d57496 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.