Triple
T16545713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court Circular |
E401936
|
entity |
| Predicate | hasUpdateInterval |
P7002
|
FINISHED |
| Object | daily on working days |
—
|
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: daily on working days | Statement: [Court Circular, hasUpdateInterval, daily on working days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpdateInterval Context triple: [Court Circular, hasUpdateInterval, daily on working days]
-
A.
hasInterval
Indicates that something is associated with a specific span or range between two points in time, space, or value.
-
B.
hasBaseInterval
Indicates that one entity has a fundamental or reference interval that serves as the base measurement or range for another related quantity or structure.
-
C.
latestInterval
Indicates that the related interval is the most recent or last occurring time span among a set of intervals.
-
D.
hasUpdatePolicy
chosen
Indicates that one entity defines or is associated with the rules or strategy governing how another entity is updated or maintained over time.
-
E.
isUpdatedWhen
Indicates that one entity undergoes a change or refresh whenever another specified entity is modified or updated.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34562c30c81908d6318f359002ff2 |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.