Triple
T29268367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jelebu (P126) |
E742040
|
entity |
| Predicate | isInPeninsularMalaysia |
P94875
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jelebu (P126), isInPeninsularMalaysia, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInPeninsularMalaysia Context triple: [Jelebu (P126), isInPeninsularMalaysia, true]
-
A.
regionInMalaysia
chosen
Indicates that a region or area is located within the country of Malaysia.
-
B.
recognizedAsMalayState
Indicates that an entity is officially acknowledged or designated as a Malay state.
-
C.
rankingByLengthInPeninsularMalaysia
Indicates a ranking relationship among items based on their lengths, specifically within the context of Peninsular Malaysia.
-
D.
locatedInFederalTerritory
Indicates that one entity is geographically or administratively situated within a federal territory.
-
E.
hasFederalTerritory
Indicates that a sovereign state possesses and administers one or more territories directly under its federal authority rather than as constituent states or provinces.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664e14c3c81908b24b54da2bc89c9 |
completed | May 2, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:46 p.m.