Triple
T32838123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zrt. |
E839891
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hungarian corporate form |
C38844
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Hungarian corporate form Context triple: [Zrt., instanceOf, Hungarian corporate form]
-
A.
Hungarian company
chosen
A Hungarian company is a legally registered business entity operating in Hungary, organized under Hungarian corporate law to conduct commercial, industrial, or professional activities.
-
B.
Hungarian law
Hungarian law is the legal system of Hungary, based on a civil law tradition that combines codified statutes, constitutional principles, and European Union legal norms to regulate public, private, and criminal matters within the country.
-
C.
Hungarian legal work
Hungarian legal work encompasses the professional activities of legal practitioners in Hungary, including advising clients, drafting documents, and representing parties in matters governed by Hungarian law.
-
D.
Flemish public company
A Flemish public company is a government-owned legal entity established by the Flemish Region or Community to perform public-interest tasks while operating under company law principles.
-
E.
supranational public limited-liability company form
A supranational public limited-liability company form is a legally recognized corporate structure created under the authority of an international or regional body (rather than a single nation-state) that allows publicly held, limited-liability companies to operate across member countries under a unified regulatory framework.
- F. None of above.
Provenance (1 batch)
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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:16 a.m.