Triple
T5892736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Records Act 1958 |
E131028
|
entity |
| Predicate | originalAccessPeriod |
P23807
|
FINISHED |
| Object | 30 years |
—
|
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: 30 years | Statement: [Public Records Act 1958, originalAccessPeriod, 30 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalAccessPeriod Context triple: [Public Records Act 1958, originalAccessPeriod, 30 years]
-
A.
ownershipPeriod
Indicates the span of time during which an entity holds ownership rights over another entity.
-
B.
documentationPeriod
chosen
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
-
C.
historicalFirstRightsPeriodEnd
Indicates the date or point in time when an entity’s initial or original rights period (such as legal, contractual, or usage rights) historically came to an end.
-
D.
timePeriodOrigin
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
E.
registrationPeriod
Indicates the time span during which registration for something is open or valid.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.