Triple
T13798105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hamarværing |
E331567
|
entity |
| Predicate | hasGrammaticalNumberForm |
P11612
|
FINISHED |
| Object | singular |
—
|
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: singular | Statement: [hamarværing, hasGrammaticalNumberForm, singular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrammaticalNumberForm Context triple: [hamarværing, hasGrammaticalNumberForm, singular]
-
A.
hasGrammaticalNumber
chosen
Indicates that an expression is associated with a specific grammatical number category (such as singular, plural, or dual) in a language.
-
B.
grammaticalForm
Indicates the specific grammatical structure or morphological form that an expression or word takes in a given linguistic context.
-
C.
hasPluralForm
Indicates that one term is the plural grammatical form of another term.
-
D.
hasScalarForm
Indicates that something possesses or can be represented in a single-valued (scalar) form rather than as a vector, matrix, or more complex structure.
-
E.
hasCaseForms
Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025be1f08190aac525d72d7dc0c3 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.