Triple
T21218265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children Act 1989 |
E522893
|
entity |
| Predicate | reformedAreaOfLaw |
P6403
|
FINISHED |
| Object | child care law |
—
|
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: child care law | Statement: [Children Act 1989, reformedAreaOfLaw, child care law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformedAreaOfLaw Context triple: [Children Act 1989, reformedAreaOfLaw, child care law]
-
A.
notableAreaOfLaw
Indicates that a person or entity is particularly recognized or distinguished in a specific field or area of law.
-
B.
legalReformer
Indicates that an entity works to change, improve, or modernize laws or legal systems.
-
C.
branchOfLaw
chosen
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
D.
juridicalCategory
Indicates the legal classification or status under which an entity or relationship is formally recognized in a juridical system.
-
E.
relatedLegalSystem
Indicates that there is an association or connection between two legal systems, such as influence, similarity, shared origin, or mutual relevance.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7347613308190a1c9f4ea51591d4b |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:42 p.m.