Triple
T30960984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goemai |
E788819
|
entity |
| Predicate | hasMajorGrammar |
P24893
|
FINISHED |
| Object | a reference grammar by Birgit Hellwig |
—
|
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: a reference grammar by Birgit Hellwig | Statement: [Goemai, hasMajorGrammar, a reference grammar by Birgit Hellwig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorGrammar Context triple: [Goemai, hasMajorGrammar, a reference grammar by Birgit Hellwig]
-
A.
hasGrammar
chosen
Indicates that an entity possesses, follows, or is associated with a particular system of grammatical rules or structure.
-
B.
hasGrammarStatus
Indicates that an entity is associated with a particular grammatical status or classification (e.g., tense, mood, aspect, or correctness).
-
C.
hasMajor
Indicates that an entity (typically a person or student) has a specific primary field of academic study or specialization.
-
D.
hasGrammarFrom
Indicates that one entity derives or uses its grammatical structure or rules from another entity.
-
E.
hasMajorLexifier
Indicates that a language has another language as its primary lexical source or main contributor of its vocabulary.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
Created at: April 29, 2026, 8:54 p.m.