Triple
T16958078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trade Marks Act (Singapore) |
E411355
|
entity |
| Predicate | harmonisedWith |
P121162
|
FINISHED |
| Object | international trade mark treaties |
—
|
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: international trade mark treaties | Statement: [Trade Marks Act (Singapore), harmonisedWith, international trade mark treaties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harmonisedWith Context triple: [Trade Marks Act (Singapore), harmonisedWith, international trade mark treaties]
-
A.
isHarmonizedWith
chosen
Indicates that two or more elements are brought into mutual agreement, balance, or compatibility so they function together without conflict.
-
B.
usesHarmonizedNumberingWith
Indicates that two entities apply the same standardized numbering scheme so their identifiers or codes are directly comparable or aligned.
-
C.
hasHarmony
Indicates that two or more entities are in a state of balance, agreement, or pleasing coordination with one another.
-
D.
homologationFor
Indicates that something is formally approved, certified, or validated for a specific use, standard, or regulatory context.
-
E.
harmonizesDefinitionWith
Indicates that one entity adjusts or aligns its definition so that it is consistent and compatible with the definition used by another entity.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01d34d08190a73ce48e9988bd97 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.