Triple
T21767758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hittite Grammar |
E537339
|
entity |
| Predicate | typeOfDescription |
P57965
|
FINISHED |
| Object | systematic description |
—
|
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: systematic description | Statement: [Hittite Grammar, typeOfDescription, systematic description]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDescription Context triple: [Hittite Grammar, typeOfDescription, systematic description]
-
A.
hasDescription
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
B.
descriptorType
Indicates that one entity serves as a descriptive attribute or classification of another entity.
-
C.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
D.
definitionType
chosen
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
E.
subjectOfDescription
Indicates that the subject is the main entity being described or characterized in a given context or statement.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031ab57808190b9af6d8f0ead1051 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.