Triple
T25224266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klingon language |
E632049
|
entity |
| Predicate | hasFirstMajorDescription |
P11875
|
FINISHED |
| Object | The Klingon Dictionary (1985) |
—
|
NE NERFINISHED |
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: The Klingon Dictionary (1985) | Statement: [Klingon language, hasFirstMajorDescription, The Klingon Dictionary (1985)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstMajorDescription Context triple: [Klingon language, hasFirstMajorDescription, The Klingon Dictionary (1985)]
-
A.
firstMajorDescription
Indicates that the object is the primary or earliest major field of study associated with the subject.
-
B.
hasMajor
Indicates that an entity (typically a person or student) has a specific primary field of academic study or specialization.
-
C.
hasSingleMajor
Indicates that an entity (such as a student or academic program) is associated with exactly one major field of study.
-
D.
hasDescription
chosen
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
E.
hasFirstVersion
Indicates that one entity is the earliest or original version in a sequence of versions related to another entity.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 21, 2026, 1:03 p.m.