Triple
T35402825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Page Corps in St. Petersburg |
E1023280
|
entity |
| Predicate | targetCareerPath |
P37798
|
FINISHED |
| Object | officers of the imperial guard |
—
|
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: officers of the imperial guard | Statement: [Page Corps in St. Petersburg, targetCareerPath, officers of the imperial guard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetCareerPath Context triple: [Page Corps in St. Petersburg, targetCareerPath, officers of the imperial guard]
-
A.
careerPath
Indicates the progression or sequence of roles, positions, or occupations that an individual follows over time in their professional life.
-
B.
targetCareer
chosen
Indicates that one entity is the intended or pursued career or professional goal of another entity.
-
C.
plannedCareer
Indicates that an individual has chosen and intends to pursue a specific career path.
-
D.
managedCareerOf
Indicates that one entity was responsible for overseeing, directing, or handling the professional career of another entity.
-
E.
acceptsCareerPath
Indicates that one entity approves or agrees to follow a proposed career path associated with another entity.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 3, 2026, 4:03 p.m.