Triple
T360412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Insurance Act 1911 |
E7837
|
entity |
| Predicate | createdSystem |
P4328
|
FINISHED |
| Object | national insurance |
—
|
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: national insurance | Statement: [National Insurance Act 1911, createdSystem, national insurance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdSystem Context triple: [National Insurance Act 1911, createdSystem, national insurance]
-
A.
createdProgram
Indicates that an entity authored, developed, or produced a particular program (such as software or a coded application).
-
B.
createdFrameworkFor
Indicates that one entity developed or established a foundational structure, system, or methodology that another entity later used or built upon.
-
C.
createdRegimeOf
chosen
Indicates that one entity brought about, established, or was responsible for the formation of a particular regime or system of rule for another entity.
-
D.
createdInstrument
Indicates that an entity brought into existence or produced a particular instrument or tool.
-
E.
notableSystem
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebccb8d88190a31f7c443a0c8566 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95aeed48190b5e48865cc964938 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.