Triple
T35541895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 85-864 |
E1027082
|
entity |
| Predicate | lawNumberingScheme |
P1117
|
FINISHED |
| Object | Public Law 85-864 |
—
|
NE NERFINISHED |
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 85-864 | Statement: [85-864, lawNumberingScheme, Public Law 85-864]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawNumberingScheme Context triple: [85-864, lawNumberingScheme, Public Law 85-864]
-
A.
legislatureNumberingScheme
Indicates how legislative bodies or sessions are sequentially numbered or labeled within a given political or legal system.
-
B.
legalNumbering
Indicates that an entity has an officially assigned legal or regulatory identification number.
-
C.
historicalNumberingScheme
Indicates that the associated numbering system or identifier reflects a past or legacy scheme that was used historically rather than the current one.
-
D.
standardNumberingScheme
Indicates that there is a specific, commonly accepted numbering system or convention being applied to identify or order the related entities.
-
E.
publicLawNumber
chosen
Indicates the specific public law identifier associated with a legislative act or statute.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.