Triple
T29301607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zero Hour in the Rajya Sabha |
E742974
|
entity |
| Predicate | formalityStatus |
P4154
|
FINISHED |
| Object | informal |
—
|
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: informal | Statement: [Zero Hour in the Rajya Sabha, formalityStatus, informal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalityStatus Context triple: [Zero Hour in the Rajya Sabha, formalityStatus, informal]
-
A.
hasFormalStatus
Indicates that an entity possesses an officially recognized or legally defined status within a formal system or context.
-
B.
hasInformalStatus
chosen
Indicates that an entity holds a non-official, casual, or unofficial standing or role in relation to another entity.
-
C.
formedState
Indicates that an entity brought a particular state, condition, or configuration into existence or caused it to come about.
-
D.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
E.
legalStatusAtApproval
Indicates the legal status or classification an entity held at the time it was formally approved.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 1:10 p.m.