Triple
T24909536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulrich Salchow |
E623807
|
entity |
| Predicate | yearsActiveAsAthlete |
P8357
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Ulrich Salchow, yearsActiveAsAthlete, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearsActiveAsAthlete Context triple: [Ulrich Salchow, yearsActiveAsAthlete, late 19th century]
-
A.
activeYearsInSport
chosen
Indicates the span of years during which an entity actively participated in a particular sport.
-
B.
activeYearsInCareer
Indicates the span of time during which an entity was actively engaged in a particular career or professional field.
-
C.
yearsActiveAsBoxer
Indicates the span of time, measured in years, during which an individual was actively engaged in boxing.
-
D.
activeYearsPeak
Indicates the span of years during which an entity was at the height of its activity or prominence.
-
E.
retiredAsPlayerFrom
Indicates that an individual ended their professional playing career while being associated with a specific team, organization, or context.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:27 a.m.