Triple
T14024036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wielki Giewont |
E337408
|
entity |
| Predicate | hasFixedProtection |
P15826
|
FINISHED |
| Object | chains on upper sections |
—
|
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: chains on upper sections | Statement: [Wielki Giewont, hasFixedProtection, chains on upper sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFixedProtection Context triple: [Wielki Giewont, hasFixedProtection, chains on upper sections]
-
A.
providesProtectionIn
Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
-
B.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
-
C.
hasStrictProtection
Indicates that an entity is subject to strong, enforceable safeguards or restrictions that tightly limit how it can be accessed, used, or altered.
-
D.
hasProtectionPurpose
Indicates that something is intended or designed to serve a protective function or goal.
-
E.
protectionType
chosen
Indicates the kind or method of protection that is applied to or associated with an 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3d87b88190b038d334f4965369 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.