Triple
T231448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 93-198 |
E4418
|
entity |
| Predicate | effectiveIn |
P6506
|
FINISHED |
| Object | District of Columbia municipal governance |
—
|
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: District of Columbia municipal governance | Statement: [Public Law 93-198, effectiveIn, District of Columbia municipal governance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveIn Context triple: [Public Law 93-198, effectiveIn, District of Columbia municipal governance]
-
A.
hasLegalEffect
chosen
Indicates that an action, document, or condition produces recognized legal consequences or enforceable rights and obligations.
-
B.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
C.
hasLegalEffectToday
Indicates that a legal rule, document, or status is currently in force and produces legal consequences as of today.
-
D.
enactedAfter
Indicates that one enactment event occurred later in time than another enactment event.
-
E.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.