Triple
T36956627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Brigade |
E914204
|
entity |
| Predicate | hasAchievements |
P192463
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Iron Brigade, hasAchievements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAchievements Context triple: [Iron Brigade, hasAchievements, true]
-
A.
hasAchievementType
Indicates that an achievement is classified under a specific type or category of achievement.
-
B.
hasMainAchievement
Indicates that an entity possesses a primary or most significant achievement associated with it.
-
C.
hasSubjectAchievement
Indicates that an entity has achieved, accomplished, or earned a particular subject-related goal, milestone, or recognition.
-
D.
hasCivicAchievement
Indicates that an entity has attained a notable accomplishment or recognition related to civic engagement, public service, or contributions to the community.
-
E.
achievementSupport
Indicates providing assistance, resources, or encouragement that helps an entity achieve goals or reach a desired level of performance.
- F. None of above. chosen
Provenance (4 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
| PDg | Predicate description generation | batch_69fd0b92150881909b1166fe6d09aa19 |
completed | May 7, 2026, 10 p.m. |
Created at: May 3, 2026, 4:13 p.m.