Triple
T860282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24 Akbar Road, New Delhi |
E18583
|
entity |
| Predicate | mediaRole |
P20270
|
FINISHED |
| Object | venue for major party announcements |
—
|
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: venue for major party announcements | Statement: [24 Akbar Road, New Delhi, mediaRole, venue for major party announcements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaRole Context triple: [24 Akbar Road, New Delhi, mediaRole, venue for major party announcements]
-
A.
broadcastRole
Indicates that an entity has a specific role or function within a broadcast or transmission context.
-
B.
mediaAccess
Indicates that one entity has the ability, permission, or means to view, use, or interact with a particular media resource.
-
C.
displayRole
Indicates the role or position an entity holds in the context of how it is presented or shown in a display.
-
D.
mediaRights
Indicates that one entity holds legal permission or authority to use, distribute, or control the use of another entity’s media content.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac52536c8190ab198232e9ec4bd6 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.