Triple
T11750583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law and Administration Ordinance 1948 |
E279392
|
entity |
| Predicate | inForceOn |
P5570
|
FINISHED |
| Object | 1948-05-19 |
—
|
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: 1948-05-19 | Statement: [Law and Administration Ordinance 1948, inForceOn, 1948-05-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inForceOn Context triple: [Law and Administration Ordinance 1948, inForceOn, 1948-05-19]
-
A.
inForceIn
Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
-
B.
inForce
chosen
Indicates that a rule, law, agreement, or condition is currently valid, active, and being applied or enforced.
-
C.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
D.
inForceAfter
Indicates that a condition, rule, or agreement becomes valid or operative only after a specified time, event, or state has occurred.
-
E.
inForceInPart
Indicates that a rule, agreement, or provision is currently effective only for some of its parts, conditions, or scope, but not in its entirety.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a508b0c4819082fbcc27d559ea2f |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.