Triple
T30724233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perlisian |
E782234
|
entity |
| Predicate | mayAlsoInclude |
P170071
|
FINISHED |
| Object | Chinese Malaysians in Perlis |
—
|
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: Chinese Malaysians in Perlis | Statement: [Perlisian, mayAlsoInclude, Chinese Malaysians in Perlis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAlsoInclude Context triple: [Perlisian, mayAlsoInclude, Chinese Malaysians in Perlis]
-
A.
mayIncludeMode
Indicates that one entity is allowed to contain or support a particular mode as one of its possible configurations or options.
-
B.
mayIncludeRequirement
Indicates that something can optionally contain or encompass a particular requirement as part of its definition or structure.
-
C.
mayIncludeFeature
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
D.
mayAlsoAdmit
Indicates that an entity has the option or authority to additionally allow or accept another entity, beyond any primary or default admission.
-
E.
mayIncludePower
Indicates that something is permitted or able to contain, involve, or provide power as one of its possible components or attributes.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c5bab9c8190b1f0518559c5259f |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:36 p.m.