Triple
T32844200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian customary law |
E840050
|
entity |
| Predicate | continuedInForceUntil |
P41751
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Hungarian customary law, continuedInForceUntil, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedInForceUntil Context triple: [Hungarian customary law, continuedInForceUntil, 19th century]
-
A.
continuedRelevanceAfterEndDate
Indicates that something remains relevant or applicable even after its specified end date has passed.
-
B.
endingPeriod
Indicates that a specified time span or process concludes at the given period or point in time.
-
C.
mayRemainInForce
Indicates that an agreement, rule, or condition is allowed to continue to be valid and effective for a further period of time.
-
D.
extendsUntil
chosen
Indicates that something continues or remains in effect up to a specified point or limit in time or space.
-
E.
maintainedUntil
Indicates that a state, condition, or relationship continues to hold true up to a specified endpoint in time, but not necessarily beyond it.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:16 a.m.