Triple
T29544029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohirric |
E749580
|
entity |
| Predicate | hasGrammarFullyDescribed |
P172158
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Rohirric, hasGrammarFullyDescribed, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrammarFullyDescribed Context triple: [Rohirric, hasGrammarFullyDescribed, false]
-
A.
hasGrammar
Indicates that an entity possesses, follows, or is associated with a particular system of grammatical rules or structure.
-
B.
hasDocumentedGrammars
Indicates that there exist written or otherwise formally recorded grammars describing the linguistic structure of the subject language or linguistic system.
-
C.
hasGrammarInformation
Indicates that an entity is associated with specific grammatical details or annotations, such as part of speech, inflection, or syntactic properties.
-
D.
hasGrammarStatus
Indicates that an entity is associated with a particular grammatical status or classification (e.g., tense, mood, aspect, or correctness).
-
E.
hasPartialGrammar
Indicates that an entity possesses or is associated with an incomplete or not fully specified grammar.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 28, 2026, 5:05 p.m.