Triple
T643094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hague Agreement Concerning the International Registration of Industrial Designs |
E16780
|
entity |
| Predicate | typicalUsers |
P7221
|
FINISHED |
| Object | industrial designers |
—
|
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: industrial designers | Statement: [Hague Agreement Concerning the International Registration of Industrial Designs, typicalUsers, industrial designers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUsers Context triple: [Hague Agreement Concerning the International Registration of Industrial Designs, typicalUsers, industrial designers]
-
A.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
D.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
E.
userBase
chosen
Indicates that one entity serves as the primary or foundational group of users associated with 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f03db7481909e49c325c5f7cdae |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0a0ab481909871461418a00be7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.