Triple
T5028692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radio Azadi |
E113240
|
entity |
| Predicate | focusTopic |
P31
|
FINISHED |
| Object | Afghan politics |
—
|
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: Afghan politics | Statement: [Radio Azadi, focusTopic, Afghan politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusTopic Context triple: [Radio Azadi, focusTopic, Afghan politics]
-
A.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
B.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
categoryFocus
Indicates that one entity is the primary subject, theme, or focal point within the broader category defined by the other entity.
-
D.
focusPosition
Indicates the spatial or logical position at which attention, concentration, or processing is currently directed within a given context.
-
E.
featuresTopic
Indicates that something (such as a work, event, or item) prominently includes, focuses on, or is organized around a particular topic.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738f2cc88190a03eebf19e407411 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.