Triple
T25620744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag Protection Act of 1989 |
E642288
|
entity |
| Predicate | statusAfterCourtRuling |
P121935
|
FINISHED |
| Object | unenforceable |
—
|
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: unenforceable | Statement: [Flag Protection Act of 1989, statusAfterCourtRuling, unenforceable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterCourtRuling Context triple: [Flag Protection Act of 1989, statusAfterCourtRuling, unenforceable]
-
A.
legalOutcome
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
B.
receivedRulingOf
Indicates that one entity has been issued or handed down an official decision, judgment, or ruling by another entity or authority.
-
C.
legalStatusAfterEvent
chosen
Indicates the legal condition or classification an entity has as a result of a specified event or occurrence.
-
D.
judicialStatus
Indicates the legal or court-related condition or standing of an entity within a judicial process (e.g., pending, decided, appealed).
-
E.
courtStatus
Indicates the current legal or procedural state of a case or matter within a court system.
- 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_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 21, 2026, 5:04 p.m.