Triple
T18199880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian orthography |
E435753
|
entity |
| Predicate | hasSortingRule |
P2846
|
FINISHED |
| Object | digraphs treated as single letters in collation |
—
|
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: digraphs treated as single letters in collation | Statement: [Hungarian orthography, hasSortingRule, digraphs treated as single letters in collation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSortingRule Context triple: [Hungarian orthography, hasSortingRule, digraphs treated as single letters in collation]
-
A.
hasSort
Indicates that one entity is associated with, or classified by, a particular sort, type, or category.
-
B.
hasOrderingMethod
Indicates that there is a specific method or procedure used to place or arrange an order for something.
-
C.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
D.
comparisonRule
Indicates a rule or criterion that defines how two or more entities are to be compared or evaluated relative to each other.
-
E.
hasRuleOver
Indicates that one entity holds authority, control, or governance over 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d610f88190b4f69b1c433ea6b1 |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.