Triple
T20497766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eisbachwelle |
E502917
|
entity |
| Predicate | typicalUserSkillLevel |
P90637
|
FINISHED |
| Object | advanced surfers |
—
|
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: advanced surfers | Statement: [Eisbachwelle, typicalUserSkillLevel, advanced surfers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUserSkillLevel Context triple: [Eisbachwelle, typicalUserSkillLevel, advanced surfers]
-
A.
typicalExperienceLevel
chosen
Indicates the usual or most common level of experience associated with an entity in a given context.
-
B.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
C.
servesSkillLevel
Indicates that one entity provides or is appropriate for a particular level of skill in another entity.
-
D.
typicalEquipmentLevel
Indicates the usual or standard amount or quality of equipment associated with an entity or situation.
-
E.
typicalIntermediateLevel
Indicates that something represents a common or standard degree of difficulty, complexity, or proficiency that falls between beginner and advanced levels.
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cbefe4c819098af5bfd4d92341d |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.