Triple
T10330497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patent Advisory Group |
E242859
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | patent policy body |
C16505
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: patent policy body Context triple: [Patent Advisory Group, instanceOf, patent policy body]
-
A.
science policy coordination body
A science policy coordination body is an organization that aligns scientific research, evidence, and expertise with policymaking processes across institutions and sectors to ensure coherent, informed, and effective public policy.
-
B.
principal organ of WIPO
The principal organ of WIPO is a primary governing body responsible for setting the organization’s policies, overseeing its activities, and making key decisions on intellectual property matters at the international level.
-
C.
PCT authority
A PCT authority is an official national or regional patent office designated under the Patent Cooperation Treaty to perform specific functions such as receiving international applications, conducting international searches, and/or carrying out preliminary examinations.
-
D.
public policy office
chosen
A public policy office is an organizational unit within a government or institution responsible for researching, developing, analyzing, and coordinating policies to address public issues and guide decision-making.
-
E.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
- F. None of above.
Provenance (1 batch)
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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:52 a.m.