Triple
T38083531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Pension |
E950915
|
entity |
| Predicate | canBeClaimedFromAbroad |
P200680
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [State Pension, canBeClaimedFromAbroad, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeClaimedFromAbroad Context triple: [State Pension, canBeClaimedFromAbroad, true]
-
A.
couldServeOverseas
Indicates that an entity has the ability or eligibility to perform service or duties in a foreign or overseas location.
-
B.
locatedInOverseasCountry
Indicates that an entity is situated in a country that is overseas relative to a given reference location or jurisdiction.
-
C.
canBePaidOverseas
Indicates that a payment or financial obligation is eligible to be made from or processed in a foreign country.
-
D.
haveOpenBordersThrough
Indicates that one entity allows unrestricted or minimally restricted cross-border movement or access via another specified entity or route.
-
E.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69ff9e90b5248190bdd8d13f966b63e1 |
completed | May 9, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:21 p.m.