Triple
T25620720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag Protection Act of 1989 |
E642288
|
entity |
| Predicate | wasEnactedAfter |
P6514
|
FINISHED |
| Object | Texas v. Johnson |
—
|
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: Texas v. Johnson | Statement: [Flag Protection Act of 1989, wasEnactedAfter, Texas v. Johnson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEnactedAfter Context triple: [Flag Protection Act of 1989, wasEnactedAfter, Texas v. Johnson]
-
A.
enactedAfter
chosen
Indicates that one enactment event occurred later in time than another enactment event.
-
B.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
C.
enactedDuring
Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
-
D.
dateEnacted
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
-
E.
wasEnactedAsPartOf
Indicates that one legislative act, rule, or measure was formally established as a component within a larger legislative package, bill, or enactment.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa204d1c8190b441d4efd8d80940 |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:04 p.m.