Triple
T38176320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAS Building |
E1000222
|
entity |
| Predicate | regulatoryRoleOfOccupant |
P138241
|
FINISHED |
| Object | central bank of 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: central bank of Singapore | Statement: [MAS Building, regulatoryRoleOfOccupant, central bank of Singapore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryRoleOfOccupant Context triple: [MAS Building, regulatoryRoleOfOccupant, central bank of Singapore]
-
A.
jurisdictionOfOccupant
Indicates the legal authority or control that an occupant exercises over a place, property, or domain.
-
B.
regulationRole
chosen
Indicates a role in which one entity regulates, controls, or modulates the behavior, activity, or state of another entity.
-
C.
politicalStatusOfOccupant
Indicates the political role, affiliation, or status held by the occupant of a given position, place, or office.
-
D.
eraOfOccupant
Indicates the historical time period during which an occupant held or used a particular place, position, or role.
-
E.
goalOfOccupant
Indicates that a particular goal or objective is associated with, pursued by, or intended for a specific occupant.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 3, 2026, 4:29 p.m.