Triple
T37610065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horezu |
E935761
|
entity |
| Predicate | hasRegionallyProtectedProduct |
P158081
|
FINISHED |
| Object | Horezu ceramics |
E2235178
|
NE 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: Horezu ceramics | Statement: [Horezu, hasRegionallyProtectedProduct, Horezu ceramics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionallyProtectedProduct Context triple: [Horezu, hasRegionallyProtectedProduct, Horezu ceramics]
-
A.
isProtectedInSomeRegions
chosen
Indicates that the entity is subject to legal or formal protection in at least one geographic region or jurisdiction.
-
B.
supportsRegionRestriction
Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
-
C.
hasNotableRegionOfExport
Indicates that an entity is associated with a specific geographic region from which it is prominently or significantly exported.
-
D.
hasRegionCode
Indicates that an entity is associated with a specific regional identifier or code.
-
E.
hasExportRestriction
Indicates that an entity is subject to limitations or controls on exporting it to other jurisdictions or parties.
- F. None of above.
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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40ba43c8cc81908d338d11c0f8ee85 |
completed | June 28, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.