Triple
T14263128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GATT security exceptions dispute |
E353573
|
entity |
| Predicate | proceduralStep |
P100318
|
FINISHED |
| Object | request for consultations |
—
|
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: request for consultations | Statement: [GATT security exceptions dispute, proceduralStep, request for consultations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduralStep Context triple: [GATT security exceptions dispute, proceduralStep, request for consultations]
-
A.
proceduralRequirement
Indicates that one entity specifies or imposes a required procedure or process that must be followed by another entity.
-
B.
stepInRoutine
chosen
Indicates that an action or event occurs as an ordered step within a larger, structured routine or sequence of activities.
-
C.
stepType
Indicates the specific kind or category of step an entity represents within a process or sequence.
-
D.
documentedProcess
Indicates that a process has been formally recorded, described, or specified in documentation.
-
E.
proceduralStatus
Indicates the current stage, condition, or progress state of a procedure or process.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de63563fc88190b0abdbf8529c65eb |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:09 a.m.