Triple
T19150551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blausee |
E468793
|
entity |
| Predicate | clarityReason |
P113054
|
FINISHED |
| Object | spring-fed water |
—
|
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: spring-fed water | Statement: [Blausee, clarityReason, spring-fed water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clarityReason Context triple: [Blausee, clarityReason, spring-fed water]
-
A.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
B.
visibilityReason
chosen
Indicates the reason or cause for why something is visible or has become visible in a given context.
-
C.
clarifiesThat
Indicates that one entity explains or makes another entity more understandable by removing ambiguity or confusion about it.
-
D.
commissionReason
Indicates the reason or justification for which a commission is initiated, assigned, or granted between entities.
-
E.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e97cfaa08190b7085d28fe970108 |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.