Triple
T364437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jobs |
E7927
|
entity |
| Predicate | capitalization |
P2204
|
FINISHED |
| Object | Jobs |
E7927
|
NE 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: Jobs | Statement: [Jobs, capitalization, Jobs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jobs Context triple: [Jobs, capitalization, Jobs]
-
A.
Jobs
chosen
Jobs is the surname of Steve Jobs, the influential co-founder and longtime leader of Apple Inc.
-
B.
CAREER
CAREER is a prestigious National Science Foundation program that supports early-career faculty in building a foundation for a lifetime of leadership in research and education.
-
C.
LinkedIn
LinkedIn is a professional networking platform and social media service focused on careers, business connections, and job opportunities.
-
D.
Glassdoor
Glassdoor is an online platform where employees and former employees anonymously review companies, share salary information, and browse job listings.
-
E.
Ed
Ed is a common masculine given name, typically used as a short form of names such as Edward, Edwin, or Edmund.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ee29ede0819095279af95b53e350 |
completed | Feb. 28, 2026, 1:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3e8668b848190b68d19819ac134df |
completed | March 1, 2026, 7:19 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.