Triple
T6393684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | post‑1987 Rule 35 |
E143888
|
entity |
| Predicate | narrowed |
P70365
|
FINISHED |
| Object | grounds for sentence modification |
—
|
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: grounds for sentence modification | Statement: [post‑1987 Rule 35, narrowed, grounds for sentence modification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrowed Context triple: [post‑1987 Rule 35, narrowed, grounds for sentence modification]
-
A.
isNarrow
Indicates that something has a small width or limited breadth relative to a reference or context.
-
B.
isNarrowestPartOf
Indicates that one entity constitutes the slimmest or most constricted section within the extent or structure of another entity.
-
C.
rinkType
Indicates the specific kind or category of rink associated with an entity (e.g., ice rink, roller rink, practice rink).
-
D.
neutralized
Indicates that one entity has rendered another entity ineffective, harmless, or no longer able to exert its intended effect.
-
E.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
- F. None of above. chosen
Provenance (4 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06881313481908e9082ffe57f29b6 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:34 p.m.