Triple
T4617119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AS/NZS 4360:2004 |
E100893
|
entity |
| Predicate | includesProcessStep |
P9959
|
FINISHED |
| Object | establishing the context |
—
|
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: establishing the context | Statement: [AS/NZS 4360:2004, includesProcessStep, establishing the context]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesProcessStep Context triple: [AS/NZS 4360:2004, includesProcessStep, establishing the context]
-
A.
hasStep
chosen
Indicates that one entity includes, is composed of, or is associated with a specific step or stage in a process involving another entity.
-
B.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
C.
disciplineProcessIncludes
Indicates that a disciplinary process encompasses, contains, or makes use of a specified step, action, or component as part of its overall procedure.
-
D.
hasProcess
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
E.
hasStepDesign
Indicates that one entity possesses or incorporates a particular step-related design or configuration in relation to 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.