Triple
T4343598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WPPT |
E97845
|
entity |
| Predicate | harmonizes |
P47812
|
FINISHED |
| Object | international standards for related rights |
—
|
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 standards for related rights | Statement: [WPPT, harmonizes, international standards for related rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harmonizes Context triple: [WPPT, harmonizes, international standards for related rights]
-
A.
hasHarmony
chosen
Indicates that two or more entities are in a state of balance, agreement, or pleasing coordination with one another.
-
B.
modulates
Indicates that one entity adjusts, regulates, or alters the intensity, frequency, or effect of another entity or process.
-
C.
hasConsonantHarmony
Indicates that the entities are related by a pattern where consonants within a linguistic unit adjust to share similar features, creating consonant harmony.
-
D.
hasVowelHarmony
Indicates that the phonological vowels in a word or morpheme conform to a systematic harmony pattern (e.g., all front or all back vowels) according to the language’s vowel harmony rules.
-
E.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35188e71c8190a3e82fa8d959de94 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.