Triple
T28668194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R'lyehian |
E725636
|
entity |
| Predicate | hasLexiconStatus |
P9130
|
FINISHED |
| Object | fragmentary lexicon |
—
|
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: fragmentary lexicon | Statement: [R'lyehian, hasLexiconStatus, fragmentary lexicon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLexiconStatus Context triple: [R'lyehian, hasLexiconStatus, fragmentary lexicon]
-
A.
lexiconStatus
chosen
Indicates the current state or condition of a lexical item within a lexicon, such as whether it is active, deprecated, provisional, or otherwise classified.
-
B.
hasLexiconSource
Indicates that a lexical item or entry is derived from, documented in, or otherwise sourced from a particular lexicon or lexical resource.
-
C.
hasLexiconPreservedIn
Indicates that the lexicon of one entity is preserved, recorded, or stored within another entity.
-
D.
hasLanguageStatus
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
E.
hasOrthographyStatus
Indicates the orthographic status or condition of how something is written or spelled, such as its conformity to a particular writing system or standard.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 28, 2026, 5:02 a.m.