Triple
T735066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States politics |
E14910
|
entity |
| Predicate | keyIssueArea |
P19540
|
FINISHED |
| Object | economic policy |
—
|
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: economic policy | Statement: [United States politics, keyIssueArea, economic policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyIssueArea Context triple: [United States politics, keyIssueArea, economic policy]
-
A.
keyFeature
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
B.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
C.
commonPolicyArea
Indicates that two entities share the same policy domain, topic, or area of regulatory or legislative focus.
-
D.
keySector
Indicates that an entity operates in, belongs to, or is primarily associated with a particularly important or strategic sector within a broader domain or economy.
-
E.
keyComponent
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fafee081909bf356854c09aaff |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a66658948190bdae6e521951954f |
completed | March 1, 2026, 8:49 p.m. |
Created at: March 1, 2026, 7:37 p.m.