Triple
T31972498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court of Judicature |
E816352
|
entity |
| Predicate | legallyCreated |
P197928
|
FINISHED |
| Object | 1873 |
—
|
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: 1873 | Statement: [Supreme Court of Judicature, legallyCreated, 1873]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legallyCreated Context triple: [Supreme Court of Judicature, legallyCreated, 1873]
-
A.
isLegallyProtected
Indicates that an entity is safeguarded by law, granting it specific rights or restrictions against harm, use, or alteration.
-
B.
legalStandardCreated
Indicates that one entity (such as a case, statute, or regulation) establishes or formulates a legal standard that is then applied or referenced by another entity.
-
C.
legalIn
Indicates that an action, status, or entity is permitted or valid under the laws or regulations of a specified jurisdiction.
-
D.
hasLegalInstrument
Indicates that there exists a formal legal document or instrument that establishes, governs, or records the relationship between the related entities.
-
E.
hasLegalProtectionSince
Indicates that an entity has been under formal legal protection starting from a specified date or point in time.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69feba0e362c81909883a3f24a4a9545 |
completed | May 9, 2026, 4:37 a.m. |
Created at: May 1, 2026, 12:10 a.m.