Triple
T38562388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Montgomery |
E928112
|
entity |
| Predicate | hasAchievementIn |
P111190
|
FINISHED |
| Object | 100-meter freestyle |
—
|
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: 100-meter freestyle | Statement: [Jim Montgomery, hasAchievementIn, 100-meter freestyle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAchievementIn Context triple: [Jim Montgomery, hasAchievementIn, 100-meter freestyle]
-
A.
hasAchievements
Indicates that an entity possesses or is associated with one or more notable accomplishments, awards, or completed goals.
-
B.
hasAchievementType
Indicates that an achievement is classified under a specific type or category of achievement.
-
C.
hasSubjectAchievement
chosen
Indicates that an entity has achieved, accomplished, or earned a particular subject-related goal, milestone, or recognition.
-
D.
hasMainAchievement
Indicates that an entity possesses a primary or most significant achievement associated with it.
-
E.
hasCivicAchievement
Indicates that an entity has attained a notable accomplishment or recognition related to civic engagement, public service, or contributions to the community.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:32 p.m.