Triple
T34785592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps civilian employees |
E1002795
|
entity |
| Predicate | hiringPath |
P181613
|
FINISHED |
| Object | competitive service |
—
|
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: competitive service | Statement: [Marine Corps civilian employees, hiringPath, competitive service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiringPath Context triple: [Marine Corps civilian employees, hiringPath, competitive service]
-
A.
careerPath
Indicates the progression or sequence of roles, positions, or occupations that an individual follows over time in their professional life.
-
B.
careerWalks
Indicates the total number of bases on balls (walks) a player has received over the course of their entire career.
-
C.
careerStation
Indicates the role, position, or stage a person holds within their professional career path.
-
D.
acceptsCareerPath
Indicates that one entity approves or agrees to follow a proposed career path associated with another entity.
-
E.
recruitmentPlatform
Indicates a relationship where an entity serves as a platform or medium used to recruit or attract candidates for positions or roles.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.