Triple
T29662528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNSO Operating Procedures |
E750448
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational procedure document |
C53016
|
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: organizational procedure document Context triple: [GNSO Operating Procedures, instanceOf, organizational procedure document]
-
A.
organizational process
chosen
An organizational process is a structured set of related activities and workflows that an organization systematically performs to achieve specific goals, deliver value, and ensure consistent, repeatable outcomes.
-
B.
organizational policy
An organizational policy is a formal, guiding principle or rule established by an organization to direct decisions, behaviors, and procedures in alignment with its goals, values, and legal obligations.
-
C.
governmental procedure
A governmental procedure is a formally established sequence of actions, rules, and decision-making steps that public authorities follow to create, implement, or enforce laws and policies.
-
D.
PCT procedure document
A PCT procedure document is a formal record that outlines the standardized steps, requirements, and workflows for filing, processing, and managing international patent applications under the Patent Cooperation Treaty.
-
E.
organizational practice
Organizational practice is a repeatable, structured way of working within an organization that guides how people coordinate, make decisions, and execute tasks to achieve shared goals.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 6:59 p.m.