Triple
T28668193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R'lyehian |
E725636
|
entity |
| Predicate | hasGrammarStatus |
P169588
|
FINISHED |
| Object | no fully defined grammar |
—
|
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: no fully defined grammar | Statement: [R'lyehian, hasGrammarStatus, no fully defined grammar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrammarStatus Context triple: [R'lyehian, hasGrammarStatus, no fully defined grammar]
-
A.
hasGrammar
Indicates that an entity possesses, follows, or is associated with a particular system of grammatical rules or structure.
-
B.
hasGrammarInformation
Indicates that an entity is associated with specific grammatical details or annotations, such as part of speech, inflection, or syntactic properties.
-
C.
hasGrammarFrom
Indicates that one entity derives or uses its grammatical structure or rules from another entity.
-
D.
hasKnownGrammar
Indicates that an entity is associated with a grammar whose structure and rules are already defined or understood.
-
E.
hasStandardizedGrammar
Indicates that a language or notation follows an officially defined and consistently applied set of grammatical rules.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 28, 2026, 5:02 a.m.