Triple
T21139313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grassmann's law |
E520887
|
entity |
| Predicate | appliesToSegmentType |
P143008
|
FINISHED |
| Object | stop consonants |
—
|
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: stop consonants | Statement: [Grassmann's law, appliesToSegmentType, stop consonants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToSegmentType Context triple: [Grassmann's law, appliesToSegmentType, stop consonants]
-
A.
hasSegmentType
Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
-
B.
appliesToServiceType
Indicates that something is relevant or applicable specifically to a particular type or category of service.
-
C.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
-
D.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
E.
appliedToGroupType
Indicates that something (such as a rule, setting, or action) is applied specifically to a particular type or category of group rather than to individual members.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235e389881908813909e05d1413a |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:57 p.m.