Triple
T23532691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judicial Commissioner (Singapore) |
E576612
|
entity |
| Predicate | hasFullJudicialPowers |
P132640
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Judicial Commissioner (Singapore), hasFullJudicialPowers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFullJudicialPowers Context triple: [Judicial Commissioner (Singapore), hasFullJudicialPowers, true]
-
A.
hasJudicialPowerLevel
chosen
Indicates that an entity possesses a specified degree or extent of judicial authority or decision-making power.
-
B.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
-
C.
hasJudicialPowerScope
Indicates the extent or domain within which a judicial authority is empowered to exercise its legal decision-making and enforcement powers.
-
D.
hasJudicialPowerSource
Indicates the source or origin from which an entity derives its judicial authority or power.
-
E.
hadJudicialFunction
Indicates that an entity exercised or was assigned an official judicial role, authority, or responsibility in relation to another entity or context.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac79800081908907bce55b9c68cf |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.