Triple
T15215600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neusiedler See wine region |
E363628
|
entity |
| Predicate | influenceFrom |
P31348
|
FINISHED |
| Object | proximity to Lake Neusiedl |
—
|
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: proximity to Lake Neusiedl | Statement: [Neusiedler See wine region, influenceFrom, proximity to Lake Neusiedl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influenceFrom Context triple: [Neusiedler See wine region, influenceFrom, proximity to Lake Neusiedl]
-
A.
influentialFrom
Indicates that one entity has exerted influence on another, contributing to or shaping the latter’s ideas, behavior, or development.
-
B.
hasLoanInfluenceFrom
Indicates that one entity’s loan terms, availability, or conditions are affected or shaped by another entity.
-
C.
influenced
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
-
D.
typeOfInfluence
chosen
Indicates the specific nature or category of influence that one entity exerts on another.
-
E.
influencedPerson
Indicates that one entity has affected, shaped, or guided the thoughts, behavior, or development of another person.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0076e4348819091fa91c1562e7c5c |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:11 a.m.