Triple
T29095505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SBGE |
E734986
|
entity |
| Predicate | emphasizesTopic |
P83753
|
FINISHED |
| Object | policy analysis |
—
|
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: policy analysis | Statement: [SBGE, emphasizesTopic, policy analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesTopic Context triple: [SBGE, emphasizesTopic, policy analysis]
-
A.
primaryTopicOf
Indicates that a given subject is the main or central topic described by another resource (such as a document, page, or record).
-
B.
hasEmphasis
Indicates that one element is given special stress, importance, or prominence relative to others.
-
C.
emphasizesPolicyArea
chosen
Indicates that one entity gives particular importance or priority to a specific policy area in its actions, statements, or focus.
-
D.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
E.
topicOfDiscourse
Indicates that something serves as the subject or focus of a particular discussion, conversation, or communicative act.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6618069888190aa87dd09a751a2c2 |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:08 a.m.