Triple
T6203858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Courts of Singapore |
E138700
|
entity |
| Predicate | currentPresidingJudgeStartYear |
P61436
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [State Courts of Singapore, currentPresidingJudgeStartYear, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentPresidingJudgeStartYear Context triple: [State Courts of Singapore, currentPresidingJudgeStartYear, 2023]
-
A.
chiefJusticeSinceYear
Indicates that an entity has held the position of chief justice starting from a specified year.
-
B.
presidingJudgeFrom
Indicates that a particular judge is serving as the presiding judge in a case, proceeding, or jurisdiction originating from a specified place or institution.
-
C.
hasChiefJudge
Indicates that an entity holds the role or position of chief judge for another entity (such as a court or judicial body).
-
D.
currentIncumbentStartYear
chosen
Indicates the year in which the entity’s current incumbent began their tenure or term in that role.
-
E.
termStartAsJudgeOfConstitutionalCourt
Indicates the date or event marking when an individual begins serving as a judge on a constitutional court.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626c23f481909d2b5b0a75c2ffff |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.