Triple
T37130026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulau Blakang Mati |
E919491
|
entity |
| Predicate | areaNowKnownFor |
P143719
|
FINISHED |
| Object | resort tourism |
—
|
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: resort tourism | Statement: [Pulau Blakang Mati, areaNowKnownFor, resort tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaNowKnownFor Context triple: [Pulau Blakang Mati, areaNowKnownFor, resort tourism]
-
A.
segmentKnownFor
Indicates that a specific segment or portion of something is recognized or notable for a particular characteristic, feature, or association.
-
B.
nowKnownFor
chosen
Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
-
C.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
D.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
-
E.
underlyingKnownFor
Indicates that one entity is fundamentally or primarily recognized as the basis or main reason for another entity’s notability or fame.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.