Triple
T33908390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raffles College |
E869247
|
entity |
| Predicate | buildingUseAfterMerger |
P177900
|
FINISHED |
| Object | University of Malaya campus in Singapore |
—
|
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: University of Malaya campus in Singapore | Statement: [Raffles College, buildingUseAfterMerger, University of Malaya campus in Singapore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingUseAfterMerger Context triple: [Raffles College, buildingUseAfterMerger, University of Malaya campus in Singapore]
-
A.
buildingUseAfterClosure
Indicates how a building is used or repurposed after its original function or operation has ceased.
-
B.
secondaryBuildingUse
Indicates how a building is used in a secondary or supplementary capacity in addition to its primary function.
-
C.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
D.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
-
E.
previousBuildingUse
Indicates that a building previously served a specified use or function before its current one.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f70519f114819080659840c04d7911 |
completed | May 3, 2026, 8:19 a.m. |
Created at: May 1, 2026, 1:48 a.m.