Triple
T28782671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PECASE |
E726715
|
entity |
| Predicate | eligibleStage |
P9657
|
FINISHED |
| Object | early 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: early career | Statement: [PECASE, eligibleStage, early career]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleStage Context triple: [PECASE, eligibleStage, early career]
-
A.
qualificationStageIncluded
Indicates that a particular qualification stage is part of, or has been included within, a broader process, procedure, or evaluation sequence.
-
B.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
C.
stageOf
chosen
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
D.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
E.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 6:20 a.m.