Triple
T23533691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night Courts (Singapore) |
E576635
|
entity |
| Predicate | hearingSchedule |
P153144
|
FINISHED |
| Object | weekday nights |
—
|
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: weekday nights | Statement: [Night Courts (Singapore), hearingSchedule, weekday nights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearingSchedule Context triple: [Night Courts (Singapore), hearingSchedule, weekday nights]
-
A.
heldPublicHearings
Indicates that formal meetings open to the public were conducted to gather input, discuss issues, or present information.
-
B.
hearsAppealsBy
Indicates that one party has the authority or role to review and decide on appeals submitted by another party.
-
C.
paroleHearings
Indicates that one or more formal hearings are held to evaluate an incarcerated individual's eligibility or suitability for parole.
-
D.
hearsProceedingsBroughtBy
Indicates that a judicial or administrative body formally considers and adjudicates legal proceedings initiated by a particular party.
-
E.
hearingsType
Indicates the specific category or kind of hearing associated with a given case or proceeding.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae14ae3c8190aa2714ea07a4658a |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:10 p.m.