Triple
T32838160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zrt. |
E839891
|
entity |
| Predicate | publicOfferingAllowed |
P198318
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Zrt., publicOfferingAllowed, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicOfferingAllowed Context triple: [Zrt., publicOfferingAllowed, no]
-
A.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
B.
offersConnectionTo
Indicates that one entity provides or enables access, linkage, or connectivity to another entity.
-
C.
usesOffering
Indicates that one entity makes use of, applies, or relies on a particular offering provided by another entity.
-
D.
offersProvision
Indicates that one entity supplies or makes available a resource, service, or benefit to another entity.
-
E.
hasOffering
Indicates that one entity provides, presents, or makes available an offering (such as a product, service, or item) to another entity or context.
- F. None of above. chosen
Provenance (4 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
| PDg | Predicate description generation | batch_69fedd5915588190bd884054e4be0414 |
completed | May 9, 2026, 7:08 a.m. |
Created at: May 1, 2026, 1:16 a.m.