Triple
T15498070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article XIII of the Pennsylvania Constitution |
E378873
|
entity |
| Predicate | legalDocumentType |
P19006
|
FINISHED |
| Object | public 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: public law | Statement: [Article XIII of the Pennsylvania Constitution, legalDocumentType, public law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalDocumentType Context triple: [Article XIII of the Pennsylvania Constitution, legalDocumentType, public law]
-
A.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
B.
legalCodeType
Indicates the specific category or classification of a legal code that applies to an entity or situation.
-
C.
documentationType
chosen
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
D.
legalAuthorityType
Indicates the specific kind or category of legal authority that governs, authorizes, or regulates an entity or action.
-
E.
legalStandardType
Indicates the specific type or category of legal standard that governs or applies to a given legal rule, decision, or evaluation.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fb0aee081909db1c54349ec8492 |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:53 a.m.