Triple
T15151712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarkes |
E361958
|
entity |
| Predicate | morphologicalRule |
P60322
|
FINISHED |
| Object | regularEnglishPluralWith-sEnding |
—
|
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: regularEnglishPluralWith-sEnding | Statement: [Clarkes, morphologicalRule, regularEnglishPluralWith-sEnding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: morphologicalRule Context triple: [Clarkes, morphologicalRule, regularEnglishPluralWith-sEnding]
-
A.
modifiesMorphologyOf
Indicates that one entity alters or changes the morphological structure or form of another entity.
-
B.
morphologicalClass
chosen
Indicates the classification of an entity based on its morphological form or structural pattern.
-
C.
notableMorphology
Indicates that an entity is characterized by a distinctive or noteworthy physical form, structure, or shape.
-
D.
relatedMorphologicalFeature
Indicates that one entity is connected to another through a shared or corresponding morphological feature or structure.
-
E.
hasVerbalMorphology
Indicates that one linguistic element exhibits verbal inflectional properties or patterns in relation to another.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00609040081908c849475a2fa6443 |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.