Triple
T34393649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minister for Finance (Incorporated) |
E882772
|
entity |
| Predicate | holdsAssetsFor |
P179156
|
FINISHED |
| Object | Government 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: Government of Singapore | Statement: [Minister for Finance (Incorporated), holdsAssetsFor, Government of Singapore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsAssetsFor Context triple: [Minister for Finance (Incorporated), holdsAssetsFor, Government of Singapore]
-
A.
holdsTo
Indicates that one entity maintains, adheres, or remains committed to another entity, such as a belief, standard, agreement, or condition.
-
B.
holdsFor
Indicates that a particular relationship or condition remains true over a specified interval or duration of time.
-
C.
holdsService
Indicates that one entity provides, maintains, or is responsible for a particular service for another entity or context.
-
D.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
E.
holdingType
Indicates the type or category of a holding or possession that one entity has in relation to another or to an asset.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:59 a.m.