Triple
T6087697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Decree of 24 March 1815 |
E135679
|
entity |
| Predicate | inForceAtTimeOfIssue |
P68575
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Royal Decree of 24 March 1815, inForceAtTimeOfIssue, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inForceAtTimeOfIssue Context triple: [Royal Decree of 24 March 1815, inForceAtTimeOfIssue, yes]
-
A.
inForceSince
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
-
B.
guaranteedIssueDuring
Indicates that one entity is contractually assured or obligated to issue another entity during a specified time period or interval.
-
C.
isIssuedFor
Indicates that something (such as a document, order, or item) has been formally created, authorized, or provided for a specific purpose, recipient, or use.
-
D.
inForceAfter
Indicates that a condition, rule, or agreement becomes valid or operative only after a specified time, event, or state has occurred.
-
E.
hasInceptionPeriod
Indicates the time span or period during which something begins or comes into existence.
- F. None of above. chosen
Provenance (4 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0578bf2508190859c2dbd4c10b316 |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:12 p.m.