Triple
T20317089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nSP |
E510406
|
entity |
| Predicate | componentStructure |
P22287
|
FINISHED |
| Object | single-tier pension |
—
|
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: single-tier pension | Statement: [nSP, componentStructure, single-tier pension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentStructure Context triple: [nSP, componentStructure, single-tier pension]
-
A.
featuresStructure
Indicates that one entity possesses, exhibits, or incorporates a particular structure as a notable characteristic or component.
-
B.
internalStructure
chosen
Indicates that one entity is a component, part, or substructure contained within the overall structure of another entity.
-
C.
structureConstants
Indicates that the given values are the structure constants specifying how basis elements of an algebra (or Lie algebra) multiply or bracket to produce linear combinations of other basis elements.
-
D.
commonStructure
Indicates that two or more entities share the same or a very similar internal organization, pattern, or arrangement.
-
E.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67788ca3c8190a3496fd54a5870d6 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.