Triple
T28639460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobbing |
E724878
|
entity |
| Predicate | purposeOfRule |
P79
|
FINISHED |
| Object | to prevent dangerous elbowing in mid-air |
—
|
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: to prevent dangerous elbowing in mid-air | Statement: [Cobbing, purposeOfRule, to prevent dangerous elbowing in mid-air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfRule Context triple: [Cobbing, purposeOfRule, to prevent dangerous elbowing in mid-air]
-
A.
purposeOfLaw
Indicates that a law exists or is designed for a particular goal, function, or intended effect.
-
B.
purposeOfRegime
Indicates the goal, function, or intended role that a particular regime is designed or established to fulfill.
-
C.
natureOfRule
Indicates the fundamental type or character of a rule, specifying what kind of rule it is or how it functions within a system.
-
D.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
E.
subjectOfRule
Indicates that an entity is governed, constrained, or described by a particular rule.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:43 a.m.