Triple
T37816697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian raising |
E942794
|
entity |
| Predicate | isRuleType |
P32462
|
FINISHED |
| Object | phonological raising rule |
—
|
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: phonological raising rule | Statement: [Canadian raising, isRuleType, phonological raising rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRuleType Context triple: [Canadian raising, isRuleType, phonological raising rule]
-
A.
typeOfRule
chosen
Indicates that one rule is classified as a specific kind or category of another, more general rule.
-
B.
typeOfRules
Indicates that one entity specifies or categorizes the kind or category of rules that apply to or are associated with another entity.
-
C.
supportsRuleType
Indicates that one entity is capable of handling, applying, or being compatible with a specified type of rule.
-
D.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
-
E.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.