Triple
T10518721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Next One |
E248105
|
entity |
| Predicate | appliedDuringCareerStage |
P50750
|
FINISHED |
| Object | junior career |
—
|
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: junior career | Statement: [The Next One, appliedDuringCareerStage, junior career]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedDuringCareerStage Context triple: [The Next One, appliedDuringCareerStage, junior career]
-
A.
isStageInCareerOf
Indicates that one entity represents a particular phase or stage within the professional career of another entity.
-
B.
supportsCareerStage
Indicates that one entity provides resources, opportunities, or conditions that are appropriate or beneficial for another entity’s specific stage in their career.
-
C.
appliesDuringCareerPhase
chosen
Indicates that something is relevant or in effect only during a specified phase of an entity’s career.
-
D.
hasStageCareer
Indicates that an entity has pursued or been involved in a professional career in stage performance or theater.
-
E.
partOfCareer
Indicates that one entity represents a role, position, or period that forms a component or phase within another entity’s overall career.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509dd29b48190aa5b170e2558545c |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:28 p.m.