Triple
T18199861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian orthography |
E435753
|
entity |
| Predicate | hasRuleType |
P95839
|
FINISHED |
| Object | word separation rules |
—
|
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: word separation rules | Statement: [Hungarian orthography, hasRuleType, word separation rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuleType Context triple: [Hungarian orthography, hasRuleType, word separation rules]
-
A.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
B.
supportsRuleType
Indicates that one entity is capable of handling, applying, or being compatible with a specified type of rule.
-
C.
typeOfRule
Indicates that one rule is classified as a specific kind or category of another, more general rule.
-
D.
typeOfRules
chosen
Indicates that one entity specifies or categorizes the kind or category of rules that apply to or are associated with another entity.
-
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.