Triple
T37063048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malaysian passport |
E917371
|
entity |
| Predicate | requiresVisaFor |
P9585
|
FINISHED |
| Object | some countries |
—
|
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: some countries | Statement: [Malaysian passport, requiresVisaFor, some countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresVisaFor Context triple: [Malaysian passport, requiresVisaFor, some countries]
-
A.
visaRequirement
chosen
Indicates whether one party must obtain a visa in order to enter, stay in, or transit through the territory of another party.
-
B.
shareVisaPolicy
Indicates that two entities apply the same or highly similar visa requirements and entry rules to travelers.
-
C.
supportsVisaOnArrival
Indicates that a country or authority allows eligible travelers to obtain a visa upon arrival rather than requiring it in advance.
-
D.
haveVisaLiberalizationWith
Indicates that there exists a mutual agreement or policy framework under which entities allow eased or visa-free travel between them.
-
E.
allowsVisaFreeAccessFor
Indicates that one party grants another the ability to enter or stay in its territory without requiring a visa.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:14 p.m.