Triple
T6757168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zapin Sarawak |
E154489
|
entity |
| Predicate | regionallyDistinctFrom |
P73316
|
FINISHED |
| Object | Zapin Johor |
—
|
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: Zapin Johor | Statement: [Zapin Sarawak, regionallyDistinctFrom, Zapin Johor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionallyDistinctFrom Context triple: [Zapin Sarawak, regionallyDistinctFrom, Zapin Johor]
-
A.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
B.
isRegionalAlternativeTo
Indicates that one entity serves as a counterpart or substitute for another within a specific geographic region or local context.
-
C.
regionException
Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
-
D.
regionalVariantOf
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
-
E.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
- 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_69c6880fd5808190be684854081e27dd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d3264b7481908816a4d19543fb7b |
completed | March 27, 2026, 6:57 p.m. |
Created at: March 27, 2026, 2:11 p.m.