Triple
T29398562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istana Iskandariah |
E745569
|
entity |
| Predicate | hasChapelOrPrayerRoom |
P34531
|
FINISHED |
| Object | royal surau |
—
|
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: royal surau | Statement: [Istana Iskandariah, hasChapelOrPrayerRoom, royal surau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChapelOrPrayerRoom Context triple: [Istana Iskandariah, hasChapelOrPrayerRoom, royal surau]
-
A.
hasChapelUse
Indicates that something is used, designated, or functions as a chapel or for chapel-related purposes.
-
B.
hasChapelLocation
Indicates that one entity serves as the physical location or site where a chapel associated with another entity is situated.
-
C.
hasChapels
chosen
Indicates that one entity contains, includes, or is associated with one or more chapels.
-
D.
hasChapelNearby
Indicates that one entity is located close to or in the vicinity of a chapel.
-
E.
hasChapelCountApprox
Indicates an approximate number of chapels associated with an entity.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 28, 2026, 2:48 p.m.