Triple
T23533086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Standard Time |
E576620
|
entity |
| Predicate | usedInTelecommunicationsStandardization |
P153142
|
FINISHED |
| Object | Singapore |
—
|
NE NERFINISHED |
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: Singapore | Statement: [Singapore Standard Time, usedInTelecommunicationsStandardization, Singapore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInTelecommunicationsStandardization Context triple: [Singapore Standard Time, usedInTelecommunicationsStandardization, Singapore]
-
A.
usedInTelecommunications
Indicates that something is employed as a component, tool, or method within telecommunications systems or processes.
-
B.
standardsUsedIn
Indicates that certain standards are applied, referenced, or followed within a particular context, process, or entity.
-
C.
usesTelecommunications
Indicates that one entity communicates with or transmits information to another by means of telecommunications technologies or networks.
-
D.
usedAsStandard
Indicates that one entity serves as the reference or benchmark against which another entity is measured, compared, or evaluated.
-
E.
usedInProtocol
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
- 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_69f1ac79800081908907bce55b9c68cf |
completed | April 29, 2026, 7 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.