Triple
T11611723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Social Pension for Indigent Senior Citizens |
E275398
|
entity |
| Predicate | targetedOrUniversal |
P9765
|
FINISHED |
| Object | targeted |
—
|
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: targeted | Statement: [Social Pension for Indigent Senior Citizens, targetedOrUniversal, targeted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedOrUniversal Context triple: [Social Pension for Indigent Senior Citizens, targetedOrUniversal, targeted]
-
A.
isUniversal
chosen
Indicates that the relationship or property holds for all relevant entities or cases without exception.
-
B.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
C.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
D.
targetedBecauseOf
Indicates that one entity is made a target of an action, harm, or scrutiny specifically due to possessing a particular attribute, identity, or characteristic.
-
E.
hasMarketingTarget
Indicates that an entity is aimed at or intended to appeal to a specific marketing audience or segment.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a043a3c08190a20cbc2ba5a8d218 |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.