Triple
T1341387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Job Corps |
E28470
|
entity |
| Predicate | hasOutcomeGoal |
P8644
|
FINISHED |
| Object | long-term employment |
—
|
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: long-term employment | Statement: [Job Corps, hasOutcomeGoal, long-term employment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutcomeGoal Context triple: [Job Corps, hasOutcomeGoal, long-term employment]
-
A.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
B.
hasManagementGoal
Indicates that an entity is associated with a specific management objective or target it is intended to achieve or support.
-
C.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
D.
missionOutcome
Indicates the result or consequence of a mission, specifying whether and how the mission’s objectives were achieved or failed.
-
E.
legacyGoal
chosen
Indicates that an entity has a long-term, enduring objective or impact it aims to leave behind beyond its immediate actions or existence.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c215fc008190b01fd8150b9f3b2a |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.