Triple
T18683594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ericsson Memorial |
E456796
|
entity |
| Predicate | subjectHasAchievement |
P111190
|
FINISHED |
| Object | designer of USS Monitor |
—
|
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: designer of USS Monitor | Statement: [Ericsson Memorial, subjectHasAchievement, designer of USS Monitor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectHasAchievement Context triple: [Ericsson Memorial, subjectHasAchievement, designer of USS Monitor]
-
A.
hasSubjectAchievement
chosen
Indicates that an entity has achieved, accomplished, or earned a particular subject-related goal, milestone, or recognition.
-
B.
hasAchievementType
Indicates that an achievement is classified under a specific type or category of achievement.
-
C.
achievementStatus
Indicates the current state or level of completion of an achievement-related goal or milestone for an entity.
-
D.
verificationOfAchievement
Indicates that one entity confirms or validates the successful completion or attainment of another entity’s achievement.
-
E.
hasMainAchievement
Indicates that an entity possesses a primary or most significant achievement associated with it.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2abf3c8190958c03066b5814af |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.