Triple
T21157209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 94-479 |
E521342
|
entity |
| Predicate | appliesRetroactivelyTo |
P36523
|
FINISHED |
| Object | Revolutionary War era |
—
|
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: Revolutionary War era | Statement: [Public Law 94-479, appliesRetroactivelyTo, Revolutionary War era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesRetroactivelyTo Context triple: [Public Law 94-479, appliesRetroactivelyTo, Revolutionary War era]
-
A.
doesNotApplyRetroactivelyTo
Indicates that a rule, law, or condition does not affect events, actions, or situations that occurred before it came into effect.
-
B.
isRetroactive
chosen
Indicates that an action, rule, or effect applies to a time period before its creation, enactment, or implementation.
-
C.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
D.
enactedAfter
Indicates that one enactment event occurred later in time than another enactment event.
-
E.
appliesToAfter
Indicates that one entity becomes relevant or applicable only after another specified event, condition, or time has occurred.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252c6db08190bcdffc3f2cfc6138 |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.