Triple
T3395845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Education Law Reporter |
E71525
|
entity |
| Predicate | typeOfLawCovered |
P6527
|
FINISHED |
| Object | federal 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: federal law | Statement: [Education Law Reporter, typeOfLawCovered, federal law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLawCovered Context triple: [Education Law Reporter, typeOfLawCovered, federal law]
-
A.
typeOfLaw
chosen
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
B.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
C.
typeOfDiscriminationCovered
Indicates that a particular kind or category of discriminatory behavior is included within the scope of protections, rules, or analysis.
-
D.
litigationType
Indicates the specific category or nature of a legal dispute or court case associated with an entity or event.
-
E.
jurisdictionCovered
Indicates that a particular jurisdiction or legal authority is included within the scope or coverage of another entity, rule, or arrangement.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb856158c81908dd7d3f1f8d6af74 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.