Triple
T11737766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Nationality Act 1948 |
E279073
|
entity |
| Predicate | definedStatusFor |
P101079
|
FINISHED |
| Object | British subjects |
—
|
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: British subjects | Statement: [British Nationality Act 1948, definedStatusFor, British subjects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedStatusFor Context triple: [British Nationality Act 1948, definedStatusFor, British subjects]
-
A.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
B.
possibleStatus
Indicates the set of statuses that an entity is allowed or able to assume within a given context.
-
C.
canonicalStatusIn
Indicates that something has a particular canonical or officially recognized status within a specified context or system.
-
D.
recognizesStatus
Indicates that one entity acknowledges or accepts the official status or standing of another entity.
-
E.
designationStatus
Indicates the current official classification or standing assigned to an entity within a defined system or process.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4ef1c4881909ad36dc27b1fe193 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.